Almost exactly 5 years ago, we announced the release of the OpenTok iOS SDK. In the years since, the product has evolved and grown into a cornerstone of the OpenTok platform. We are still pushing towards ever more endpoints today, as we were then. Some amazing things have happened over this history; let’s have a look at the highlight reel.
Plenty of communications tools were available for end-users back in 2012, but none exposed face-to-face communications to the mobile developer. Within a month of our release, we saw the launch of the first mobile dating app that used our service, Date.fm.
We are excited to announce the release of the OpenTok 2.9 Android and iOS SDKs. We’ve made a number of important changes with this release.
With this version your client can now automatically reconnect to OpenTok sessions after drops in network connectivity. This feature helps restore connectivity during transitions between network interfaces such as Wi-Fi and LTE, allowing you to expand the duration of the communication and provide a better quality of experience to your customers. You can find sample code showing you how to update your application here.
We’re excited to announce the release of the 2.8 OpenTok iOS and Android SDK. We’ve made significant improvements to audio/video quality, worked on bug fixes, as well as quality improvements introduced in the Google WebRTC M49 release. In order to improve the quality of these SDKs further, we’ve also rolled out some important patches, the details of which are below, including support for IPv6 for iOS.
We’re happy to announce that we recently made available OpenTok mobile SDKs 2.7.0 for iOS and Android. Improvements have been made in three main areas: Xcode 7 and iOS 9 support, quality and reliability and ease of use of the library.
Now let’s jump into all the details:
Xcode 7 and iOS 9 support
A beta bitcode version of the OpenTok iOS SDK is now available here. For more information about this update you can check out our blog post. If you have any comments or need to report any issues, please contact us at: email@example.com.
We’re happy to announce the release of the OpenTok 2.7.1-beta.1 Bitcode version.
Apple added Bitcode binary support for developer apps as part of the app thinning process. The reason behind this is to minimize the end user download app size. Prior to Xcode 7 & iOS 9, developers upload the native binary and it’s the final executable that users download.
While blind people are able to go about their day just like anyone else, simple everyday tasks can often present challenges. Whether it’s identifying the right public transit route for a commute, checking the expiration date of a carton of milk, or grabbing the right ingredients from the pantry for a meal, it may require assistance.
Founder of non-profit organization Be My Eyes, Hans Jørgen Wiberg, spent three years working for the Danish Blind Society consulting people about how to cope with visual impairment. Wiberg, who is visually impaired himself, found one common thread among all of the people he worked with: while the visually impaired often lean on friends and family to help them overcome everyday hurdles, they at times feel guilty asking for assistance. If they just ‘had a pair of eyes’ once or twice a day, they could accomplish a whole lot more on their own, without leaning on those closest to them.
In our previous post about packing more punch into the OpenTok platform we talked about a new release cadence and support policy. In order to improve our users’ experience of the OpenTok platform, we will now provide support for the current and previous versions of the client libraries.
As a quick follow up to this, we’re announcing the first set of client libraries that we will no longer be supporting.
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.
OpenTok Mobile SDKs, Revision 2: The Video Driver
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.
Yesterday, the talented folks at Double Robotics rocked the stage at LeWeb in Paris. David Cann, Co-founder and CEO, demoed their telepresence robot, Double. The sleek Double combines Segway-style movement with video presence delivered through an iPad.
Leveraging OpenTok’s iOS SDK on WebRTC, Double enables owners to broadcast their video stream on the robot’s iPad from any location. Not only that, but the operator can stream and control its movements from a smartphone.
Cann demoed the Double’s original inspiration, which was to connect remote workers with their home offices. Calling his CTO back in Sunnyvale, Cann took their Double for a three a.m. spin around the office from Paris. Customers are also finding uses for Double for remote tours of factories, museums, schools, and retail outlets.