We’re incredibly pleased to announce that OpenTok on WebRTC supports Google’s just-released Chrome 29 for Android. This brings Android support formally into the OpenTok on WebRTC family, and is a big step forward in increasing the number of WebRTC-ready endpoints in market.
We’ve been working with the Chrome for Android beta builds over the last few months, making sure that OpenTok on WebRTC works properly – and transparently – in that environment. In fact, attendees at WebRTC Expo in Atlanta saw us demonstrating OpenTok applications running in Chrome on Nexus tablets at the beginning of the summer.
As is the case on all mobile platforms, WebRTC consumes a lot of the capacity of an Android device. Lower-end Android devices will be challenged to support face-to-face video. More modern devices have anecdotally seen success, and as performance of WebRTC in Chrome for Android improves the device set supported by OpenTok will expand.
Using OpenTok on Chrome for Android also shows off one of our more recent innovations for improving the WebRTC user experience – traffic shaping in low bandwidth environments. Traffic shaping is a capability delivered by our Mantis beta infrastructure. Our infrastructure monitors connectivity statistics on a per-connection basis, and automatically switches the worst performing stream to audio-only when a device is struggling to maintain quality in the conversation. These kind of conditions are more likely to happen in a mobile environment.
With yesterday’s stable release of Chrome for Android, and our accompanying support for OpenTok on WebRTC, we’ve taken a big step forward for the OpenTok ecosystem.
Learn more about what was included in the Chrome 29 and Chrome for Android release.