OpenTok iOS and Android SDKs 2.2 into production


Following on from our OpenTok archiving and storage announcement we’re excited to fill you in on some updates we are making to our OpenTok iOS and Android SDKs 2.2 that are going into production.  What started out as internal engineering project has paved the way to the release of a suite of valuable mobile features which have become a formal part of the product offering, setting OpenTok further apart from other WebRTC platforms.

Here are some of the details:

OpenTok iOS and Android SDKs 2.2:

– Deeply integrated in OpenTok infrastructure and interop with other endpoints

– Provide support for relayed and media routed calls

– Take advantage of OpenTok firewall traversal and media routing

– Support OpenTok Intelligent Quality Controls and Messaging

– Highlight UX/UI and code best practices for real time video communications

– Include Video Driver API. To find out more, take a look at our deep dive into the Video Driver.

OpenTok Android SDK 2.2 is our first Android WebRTC SDK, which provides out of the box support for ARM and x86 based devices.

From this point, we are encouraging all OpenTok users to move to 2.2 across all endpoints: OpenTok.js, iOS and Android SDKs. We will be supporting and developing 2.2 for the foreseeable future and we will not be maintaining OpenTok.js 2.0 or OpenTok iOS 2.1.7 (with a few exceptions).

Please note that 2.2 versions introduced several architectural changes, which affect the API. We put together migration guides to help you with the transition:

– OpenTok iOS SDK 2.1.7 to 2.2:

– OpenTok.js 2.0 to 2.2:

If you have any questions about the changes, please refer to our forums:

– OpenTok iOS SDK:

– OpenTok Android SDK:

We’re really excited about the possibilities that will result from these changes and we are already seeing partners come up with some exciting developments. We look forward to getting some feedback from you and seeing what our community can do with these new features!