The OpenTok Platform started out as a real-time video communications platform, built to take on the changing landscape of digital communications. Throughout the years, one thing has always been clear to us: each use case that integrates the OpenTok platform has its own unique set of needs. Occasionally that means that video isn’t the communications medium to lead with. Sometimes voice is more than enough.
We’ve been working hard to keep those use cases in mind. Whether on mobile devices or the web, these voice-only experiences present their own unique technology and UI challenges. That’s why the OpenTok platform has a comprehensive voice offering with those use cases in mind.
Today we’re pleased to announce support for Internet Explorer versions 8 & 9 through our OpenTok Plugin. (The previous version of the plugin supported Internet Explorer 10 & 11.) Now you can leverage the same native WebRTC features enjoyed by Chrome and Firefox users in Internet Explorer versions 8 through 11.
Our release today means that your OpenTok powered applications will automatically start working with Internet Explorer 8 and 9. As always, we’re focused on bringing the best possible real time communications experiences to the endpoints you know and use. This is just one more step forward in our journey towards making the OpenTok platform endpoint agnostic.
Today we’re excited to release the OpenTok Android SDK 2.2 Beta that includes:
- API Updates.
- Archiving integration.
- Updated UI.
- Bug fixes and improved stability.
Full details about the changes can be found in the download link below.
Download our Android SDK >
At the same time we have released an updated version of our demo app to the Google Play Store – OpenTokRTC for Android. It now offers support for multi-party calling and includes examples of messaging best practice. You can access its source code on GitHub, and it’s available for download now.
Over the last several months, we’ve focused on why end-users have difficulty connecting to OpenTok sessions to try to understand how we can make this easier.
We discovered that the first hurdle many end-users run into is properly allowing hardware access. On average 25% of Google Chrome and 5% of Mozilla Firefox publishers fail due to not allowing access to their camera and mics. Some of you have already tried to solve this problem on your own by creating a custom UI that highlights the prompt. However, the OpenTok platform should solve this problem for you and your end-users.
Today we are releasing the OpenTok iOS SDK 2.2 Beta 3 that includes:
- Archiving integration
- Updated UI
- Bug fixes and improved stability
Learn more about our iOS SDK >
This update will be available to developers starting today.