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.
At TokBox we’re always trying to find ways to improve your development experience. We pride ourselves on offering clear documentation, helpful tutorials and tools to accelerate the integration of OpenTok. We don’t plan on stopping there.
Now, with the Video Chat Embed, you can take your proof of concept from zero to sixty with a simple copy and paste.
Why is this so powerful? As the market and demand for live video communications grows, two trends are emerging. First, developers with varied coding skill levels want to build with WebRTC. Second, developers want to be able to show off a proof of concept quickly. Enter the Video Chat Embed.
To get started simply login to your TokBox account, click “Video Chat Embeds” in the left navigation and “Create New Embed”.
Make a few configuration choices for your Video Chat Embed – specify what size you would like the frame to be and what website your project will be embedded into. We’ll then generate code for you that can be added to your website in a matter of minutes.
Many of our partners eventually find themselves asking how to tell whether their users tend to experience good quality while using the OpenTok Platform. As time has taught us, this can be a difficult question to answer. The most common source of complaints stem from underwhelming audio/video (A/V) quality between endpoints. These complaints are nearly always rooted in issues with performance of the endpoint network. The correlation between network performance and A/V quality has been accepted as an industry standard. In fact, we have built tools to expose network performance data, as a proxy indicator of subjective quality. While objective data about a network may be easy to collect, it is much more difficult to assign a number to represent the quality of experience that a user subjectively experiences.
Mobile applications are rapidly becoming the primary channel through which people get things done. At the same time, user experience expectations for mobile applications far exceed expectations for applications delivered through other channels. Users expect value, ease of use and a delightful experience, but too often their expectations are not met. This is only exasperated in applications with a real-time communication component. Our customers are not immune to this trend; an increasing number of them are building applications with a mobile-first strategy and it is becoming a significant part of the traffic that we see on our platform. In fact, more than 60% of the traffic we see on OpenTok is from customers using our Mobile SDKs.
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.
We have been working on a new standards-based alternative to authenticate with the OpenTok REST endpoints. With the release of the latest OpenTok Server SDKs, we will be transitioning to JSON Web Tokens (JWT) to authenticate OpenTok REST endpoints.
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.
Despite the fact that filters are used a lot in non-WebRTC video applications like Photo Booth and SnapChat, we haven’t seen many WebRTC applications using these types of filters. This is probably because it hasn’t really been possible… until now.
It has always been possible to apply filters to video streams locally using the OpenTok platform by rendering the video into a Canvas element. The problem with this approach has always been that the person on the other end does not see the filter unless you apply the same filter on both the publisher and subscriber video. This would mean significant CPU load if you are subscribing to multiple participants. It also means that you don’t get to see the filters in the Archives.