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.
In the latest versions of the OpenTok SDKs for iOS and Android, everything is new. We found an opportunity to learn from the lessons of the past two years, and seized it to conduct an overhaul of the architecture of the client. The 2.2.0 release of the iOS and Android SDKs marks the second major revision of the implementation of the OpenTok Mobile SDKs. This post highlights one of the many new features of the 2.2.0 SDKs, about which we are feeling particularly excited: the “Video Driver”. Although the feature exists with parity in both platforms, today we’ll focus on the iOS-variant of the new API.
Here at TokBox HQ we’ve spent the past couple of weeks getting excited and getting ready for the WebRTC Conference & Expo taking place in Atlanta June 17-19. For those who have not been before, this semi-annual expo is the longest running WebRTC event where attendees have the opportunity to meet service providers, attend training sessions, learn about the latest developments and hear from industry experts.
Here at TokBox we are always trying to expand and improve our range of features, tailoring these features in line with real world developer needs. That’s why we are excited to announce some pricing and storage updates.
We’re still receiving a lot of feedback on our beta so we’d like to extend a big ‘thank you’ to our community for this.
Last year TokBox asked over 1,000 professionals from around the world about WebRTC. We wanted to find out how people were using it, the projects they were working on and their plans for making use of WebRTC in the future. It was interesting to find out about the various use cases and we learnt a lot about what people hoped to see from the platform in the future.