In the past decade, technology innovation has been one of the main catalysts for change in the way that we work. Tools like email, instant messaging, Skype, productivity and task management systems are making it easier than ever to stay connected (and focused) outside of the office – whether you’re at home, a coffee shop, or in a plane, train or automobile.
According to one estimate by the American Community Survey, telecommuting has risen 79 percent between 2005 and 2012 and now makes up 2.6 percent of the American work force, or 3.2 million workers. Two+ years later, you can imagine how much this has increased.
“Real life is, to most men, a long second-best, a perpetual compromise between the ideal and the possible.” – Bertrand Russell
The world has indeed changed in the last year as WebRTC has made massive strides both from a standardization and from a market adoption point of view. A whole host of innovative applications are succeeding on mobile and desktop end-points.
But despite another 12 months of progress, one of the key points of contention that remained stubbornly unresolved was the great video codec debate: Should VP8 or H.264 be the Mandatory-to-Implement Video Codec for WebRTC? It was a welcome and surprising move that led the IETF Working Group to finally arrive at the following consensus just last week:
Here at TokBox we are preparing for the fifth WebRTC expo, taking place in San Jose next week from 18-20 November.
Since the last WebRTC expo in June, there has been a lot of action in the market;
For those who might not know (and are still interested in the topic?) ORTC, Object RTC, is an initiative that was started one year ago by a group of people who were not comfortable with the approach taken for the design of the WebRTC APIs. This group recently published the first official draft of an alternative API including support from very relevant people from Google and Microsoft.
Signaling between client end points has always been an important facet for most interactive web applications. The use cases range from text chatting to multiplayer games to driving a robot remotely. In the world of HTML5, most developers establish signaling through websockets, long polling and server side events. However with the advent of WebRTC, data channels joined the ranks and the question posed by many developers is “Where do data channels fit in the equation?”
Data Channels provide a way to send binary / text data to another peer over the browser. The data channel api is very similar to web sockets when it comes to sending different types of data. It works peer to peer without the need of a centralized server or an additional hop in most cases.
When creating new services and products, organizations always face a challenge whether to buy or build key underlying components and functionality. As WebRTC attracts an increasing degree of interest, we regularly hear from customers that they are considering the trade-off around the decision to buy or build. Many go so far as to try and build their own real time video or audio solution before they turn to a hosted platform like OpenTok. Not surprisingly given the business we are in, we come down pretty strongly on the side of leveraging a hosted service.