We’re excited to announce the release of the OpenTok One-to-One Sample Application across web, iOS and Android. This open-source application enables you to speed up your development efforts to set up interoperable, production-quality audio/video communication between users.
As you get started with this OpenTok sample, you will learn the best practices used to develop and manage the audio, video, and camera elements on mobile devices or in the browser. We recommend this is as your first step in delivering Real Time Communications (WebRTC) solutions on the OpenTok platform.
In today’s hyper-connected world, individuals are increasingly looking to online services and solutions to give them more flexibility in their day-to-day life. Industries across the board are now operating online to meet the needs of today’s consumers and make their services more accessible – from e-commerce through to banking.
The healthcare and wellness industry is no exception. Patients can already visit the doctor virtually through their smartphone, or communicate with a specialist on the other side of the world without leaving the comfort of their own home.
But one area which has traditionally relied on physical presence has been exercise. You have to go the gym to get fit, right? Not any longer. This status quo is being disrupted by technologies such as WebRTC and embedded communications, where real-time video makes working out from home not only possible, but also personalized, effective and enjoyable.
When developing applications, the importance of mobile cannot be underestimated and, at TokBox, we recognize the need to communicate seamlessly between desktop and mobile devices. That’s why we were excited to attend Mobile World Congress last month and demonstrate the power of WebRTC in bringing contextual, embedded communications to a range of uses cases, across multiple devices.
Mobile World Congress this year surpassed a record 100,000 visitors from around the world. With a range of exhibitors and presentations from industry leaders including Facebook’s Zuckerburg and Cesar Alierta from Telefónica, the event showcased the latest technology and trends in the mobile world, from WebRTC to virtual reality and robotics.
Whether you’re developing a new website, building an app for mobile or working out web infrastructure, it’s important to keep up to date with all of the technologies contributing to the evolution of the web. The O’Reilly Fluent Conference aims to to help you do that. With a range of speakers across a number of different roles and industries Fluent covers the full scope of the Web Platform and its associated technologies.
As the WebRTC landscape continues to evolve it can be hard for developers to keep up. The Kranky Geek WebRTC event aims to fill in the gaps and jumpstart your knowledge about WebRTC and the ever-changing landscape of communications online.
The event has a jam-packed agenda with experts talking about a range of different topics from the very basics to real world applications, and building workshops. TokBox CTO, Badri Rajasekar, will be there to talk about the need to push the boundaries of WebRTC in order to cater to unprecedented broadcast use cases.
This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.
When WebRTC stuff is really broken, it gets fixed very quickly.
Early in December 2015, shortly after the release of Chrome 47 to the general public, we started to notice a subtle and strange behavior in the Audio/Video of streams during our many daily meetings using WebRTC: the video occasionally wouldn’t stay caught up with the corresponding audio. As with many bugs noticed internally by developers, it took a while for any of us to believe that what we were seeing was a real issue. We call this the inverse of productive dogfooding: rather than assume we are just like our users, we can just as easily decide we are nothing like them.
Have you ever had to support a WebRTC application and needed to get packet dumps from the user? Wireshark is a great tool for this, but asking a user to install it and make a dump rarely works. It’s just too complicated. So I was pretty excited when I read the Chrome 49 release notes which described (not in much detail) a new feature called the ‘RTC event log’. This is described as follows:
We now provide a new debug option in chrome://webrtc-internals for tracing internal details (e.g., BWE, jitter buffer state) for audio and video sessions. This option creates a log containing the timing and headers of packets as well as the timing of various internal events. We hope this will help resolve issues related to media transport and jitter buffers; attaching this log when reporting such issues will help us tremendously.
Early December saw the roll-out of Chrome 47. When doing anything with WebRTC, this is always an interesting time. A release brings new features or may break things, like removing the getUserMedia functionality for insecure origins.
Our metrics clearly track such roll outs as seen below:
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).