Why? Because all the user really knows is that her video conferencing call just failed. To build a successful, scalable service, we have to invest in infrastructure to address and solve the plethora of problems customers run into, even if those problems are in parts of the stack we don’t control.
#Highfive video conferencing at bar Bluetooth#
And it’s among the most demanding of applications at the top of that stack, in terms of its bandwidth, latency and jitter requirements.Ī simplified summary of this technology stack looks a little like this: applications, real-time audio/video codecs, call state and signaling, operating systems, hardware endpoints, cameras, microphones, Bluetooth headsets, headphones, wifi, routers, firewalls, proxies, hops, internet service providers, data centers, cloud service layers, the bridging between legacy phone networks and an IP network that wasn’t designed for real-time applications in the first place.
Video conferencing sits on top of a deep technology stack to deliver its functionality. Take responsibility for issues that aren’t necessarily your own So rolling 25- or 50-way caller support may be necessary despite the fact that few calls of that size take place. Seems like a fair bar, but there is still that pesky 10 percent that needs more. For example, 90 percent of calls could be between groups of five people or less, so you may only feel they need to support something like 8-way calls only. Even if your team of designers and engineers show you data around why only a tiny part of the population uses cruises control. That means predecessor technologies create a very high floor for “minimum features required.” You’ll include the cruise control in your new car because everyone else does. You’ll have to include features from existing cars even if they are only used by 10 percent of people-like cruise control. What does that mean? Say, you want to build a new car. Prevailing wisdom in developing a new product is that a company should focus on making 90 percent of use cases awesome and ignore the 10 percent that doesn’t add to the value proposition. The tyranny (and necessity) of the 10 percent
Here are four lessons I’ve learned along the way on why video conferencing sucks and what we can do to make it the new tech hero. Meanwhile, the state of video conferencing is abysmal.įour and a half years ago, my co-founder and I decided to enter the world of video conferencing anyway. Some of the brightest minds are creating crazy technology around us – plant-based meat, cancer detecting therapies, reusable rockets. What gives?Īs the founder of a video conferencing startup, I wholeheartedly agree with St. He asks how we live in a world where we drive Teslas and VR is more than a possibility, yet video conferencing is stuck in the dark ages. John posted an acute rant on video conferencing.
0 kommentar(er)
