Today, it is easier than ever to get involved in real-time communications, using WebRTC. For those considering investing in a mobile strategy, the technology ecosystem has never been more ripe for rapidly integrating WebRTC into your application, or even starting a project afresh. Using existing build tools like Cocoapods to get started quickly with the OpenTok iOS SDK, and the new CallKit framework introduced in iOS 10, now is the best time to jump in and start building.
Lately, we have been thinking and talking about broadcast in multimedia. By now, you might have seen that TokBox is powering applications that go beyond the contemporary one-to-one and small group settings that are typically associated with the current generation of WebRTC apps, to a much larger scale of hundreds or even thousands of people watching and participating in the conversation. At a glance, this might not sound particularly groundbreaking; video has been distributed to large audiences for years. However, a closer look is necessary: with a shift in the underlying technology, TokBox adds the option of real-time communication to the existing large-audience reach of broadcast video, to enable a whole new class of applications.
Today, we are excited to announce that version 2.3.0 of the OpenTok iOS SDK is available to our developers.
In addition to support for iOS 8 and Xcode 6, we also want to share details about additional new mobile features which we’ve outlined below.
- Build Voice-optimized experiences: Audio Levels API and UI best practice example. See more.
- Audio Driver API: implement custom Audio I/O in your app.
- Support for the armv7s architecture.
- Support for the iOS Simulator.
- Intelligent Quality Control features:
- Video recovery from audio-only fallback.
- Connection Quality API: a warning callback to notify that audio-only fallback is eminent.
- Audio-only fallback redesign.
Learn more about OpenTok iOS SDK 2.3.0 here.
Last night TokBox released patches to the OpenTok iOS and Android SDKs to resolve a recently identified OpenSSL vulnerability that affects the majority of web service providers.
‘An attacker using a carefully crafted handshake can force the use of weak keying material in OpenSSL SSL/TLS clients and servers. This can be exploited by a Man-in-the-middle (MITM) attack where the attacker can decrypt and modify traffic from the attacked client and server.’
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.