GUEST POST: WebRTC.ventures is a custom design & development agency focused on building WebRTC applications. They are part of AgilityFeat, which is one of our development partners at TokBox. Jean Lescure from their team wanted to share their experiences using our new API for detecting call quality.
Back in August TokBox announced their new Pre-Call API, for testing out bandwidth conditions, and posted a repository on github with a proof of concept. At WebRTC.ventures we saw a great opportunity to build upon that project and got working on creating a demo app out of it, including a server implementation in NodeJS which is compatible with Heroku.
At our September TechTok WebRTC consultant and analyst, Tsahi Levent-Levi, came along to discuss the power plays of the video coding industry.
Just when we thought we were done with the video codec wars in WebRTC – we found out we’re only just beginning. Tsahi was here to talk us through some important questions – how is this WebRTC codec war going to play out? Where do the alliances lie? And where are we headed?
Watch the full video here:
UPDATE 9/16/15: After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.
Google recently announced a security policy change that will impact future versions of the Chrome browser. Any website which has integrated geolocation technology, screen-sharing, WebRTC and more, will now be required to be served from a secure (HTTPS) site.
We at TokBox are supportive of this update as we believe operating your WebRTC-based applications through HTTPS is a best practice and offers enhanced security. In addition, it has the added bonus of improving your end-user experience by remembering their hardware settings, and even allowing screen-sharing (if you choose to implement it).
Just when we thought we were done with the video codec wars in WebRTC – we found out we’re only just beginning.
In the past several weeks we’ve seen the names Thor, Daala, VP9 and H.265 thrown in the news as potential candidates to replace our current generation of video codecs. How is that going to play out, and where are we headed with all this?
About a year ago we found ourselves scratching our heads trying to find a place that would give developers easier access to all of the tools that they need to get started with OpenTok. We already had a section for documentation but a lot of the tools and materials that we were working on didn’t really fit into the structure that we had. At the same time, we wanted to relaunch our website to better explain what TokBox can do for you, your product and your business.