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.
Across many industries and use cases, developers on the OpenTok platform are creating live video applications that enable life changing experiences. Whether it is doctor-patient care, online tutoring, high-touch customer service, team collaboration, social interactions, or interactive broadcasting, developers are bringing people together worldwide in ways that were not previously possible.
Our customers are building their businesses on the OpenTok Platform. To meet the needs of increasingly sophisticated applications we’re introducing additional server-side REST APIs that give developers more dynamic control over the OpenTok Platform — the Session Management and Account Management APIs.
Today we’re rolling out our new Windows SDK into public-beta. This means that you can build live video applications and services that work seamlessly across iOS, Android, Web and Windows desktops, laptops, and tablets. With this, TokBox is continuing to broaden our endpoint flexibility for our customers and partners.
The Windows SDK has all the great features that you’ve come to expect from the OpenTok Platform. In addition to being fully interoperable with all our existing client SDKs, it also includes support for:
- C# API for Windows C# developers
- .NET 4.6.1
- OS versions: Windows 7, Windows 8.x and Windows 10
- x86 and x64 architectures
- Custom video capturer
On Saturday March 11th, TokBox joined Ziggeo to co-host the third annual Video Hack Day at General Assembly in New York City. The one-day hackathon event saw creative web and mobile developers from the New York area and beyond come together and use the latest video technologies to rapidly build innovative and exciting applications.
By all accounts, the event was a resounding success, with over 100 ‘hackers’ submitting projects that ranged from highly practical civic solutions to online dance party platforms (which is not to say that dance isn’t practical). With a tight window of around 10 hours to complete a fully demo-able product, the participating teams were pushed to their limit, and the results were more than impressive.
Last year TokBox introduced the OpenTok Interactive Broadcast API. Ours became the first platform to marry the real-time capability of WebRTC with the reach of HTTP Live Streaming (HLS). The Interactive Broadcast API is helping our customers build large-scale interactive video experiences including live online auctions, Massive Open Online Courses (MOOCs), webinars, social apps and more.
Over the past 6 months we’ve continued to innovate in the broadcast space, pushing the boundaries of performance while ensuring massive scale. Today we’re proud to announce major enhancements to our Interactive Broadcast API.
TokBox is pleased to be sponsoring the upcoming Kranky Geek WebRTC Tour across Bangalore, Hyderabad and Chennai in India during March 2017 (see below for dates). This fast-paced event brings respected WebRTC and real-time communications experts to town to help technologists and developers quickly get up-to-speed on the opportunities to enhance apps with global live video experiences using WebRTC.
Why traditional broadcasters need to adapt, fast
Cable companies and television networks can’t take a trick at the moment. As if digital disruption and cord cutting wasn’t making life tough enough, now comes the rise of participatory broadcasting, the phenomena where viewers collaboratively interact while consuming content, and maybe even participate.
Still coming to grips with on demand and online/mobile viewing, traditional broadcasters must now find a way to provide immersive and engaging viewer experiences to compete with the likes of Facebook Live, Meerkat and Periscope.
Web Application Developers are used to being able to write automated tests for their applications and have them run with every PR and before deploying to production to give a level of confidence that things are not broken. OpenTok and real-time applications in general present new challenges when it comes to writing and running automated tests. There are challenges when it comes to getting access to microphones and cameras, testing multiple participants and installing the plugin for Internet Explorer among others.
There has been lots of work around WebRTC testing automation and our friends at rtc.io and &yet have written some great articles on the subject. However these articles don’t cover some of the specifics of testing OpenTok applications for example testing Internet Explorer and installing the OpenTok plugin for Internet Explorer. If you haven’t already I would recommend taking some time to read the articles by the folks at rtc.io and &yet before coming back to this. Also if you’re not familiar with Travis and Selenium WebDriver you might want to check those out too.
We all have a fascination with the billion dollar startups. Venture Capitalists try and identify them early, media laud them (or bring them down to earth), and early adopters claim discovery. One new technology innovation has the potential to spark the creation of more billion dollar companies, and markets are starting to pay attention. So what is WebRTC, and why is there so much interest?
It begins with recognizing the emergence of two massive trends. The first is the increasing appetite for ‘on demand’. This is evident in everything from movies to car rides, hotels, relationships to groceries to well, everything. And communications is a core part of this, just look at Meerkat and Twitter’s latest acquisition, Periscope, bringing
This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.
When WebRTC stuff is really broken, it gets fixed very quickly.
Early in December 2015, shortly after the release of Chrome 47 to the general public, we started to notice a subtle and strange behavior in the Audio/Video of streams during our many daily meetings using WebRTC: the video occasionally wouldn’t stay caught up with the corresponding audio. As with many bugs noticed internally by developers, it took a while for any of us to believe that what we were seeing was a real issue. We call this the inverse of productive dogfooding: rather than assume we are just like our users, we can just as easily decide we are nothing like them.