Mozilla has released further enhancements to Firefox Hello, powered by OpenTok, including the ability to screen share within a video chat. This new feature allows participants to open and share a browser tab or application window from within the chat, making browsing, shopping, drafting or any other activity more collaborative and engaging.
We’re moving the OpenTok Platform to a new release cadence – less frequent with more punch. We’ve made a few significant decisions about how we’re going to release and support client updates in the OpenTok Platform, and, as these changes go live, we wanted to keep the OpenTok community properly updated.
Over the life of the OpenTok Platform, we’ve moved from weekly to bi-weekly to monthly releases. When the Platform only had web-based clients, it was possible for us and (some of) our partners to move this quickly.
As an OpenTok customer, you know that in order to deliver a great call experience, network connectivity is king. You can spend hours developing your real-time communications app, only to encounter connectivity hurdles like corporate firewalls or blocked IP in a new network environment.
It’s important to know that your application will work where you need it to, whether you’re pitching an investor, selling to a client, or just showing off all your hard work. That’s why we’re excited to launch the first version of the OpenTok Connectivity Doctor.
The OpenTok Connectivity Doctor helps you diagnose problems with your network before or after you connect to an OpenTok session. This tool does not test for errors in your code.
Hot off the heels of our OpenTok 2.0 Archiving API pricing and storage announcement we’re excited to announce that our Archiving API has now gone into production.
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.
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.
Here at TokBox we are always trying to expand and improve our range of features, tailoring these features in line with real world developer needs. That’s why we are excited to announce some pricing and storage updates.
We’re still receiving a lot of feedback on our beta so we’d like to extend a big ‘thank you’ to our community for this.
While WebRTC has been innovating at an impressively rapid rate, the users of the web and mobile apps have been delighted with lots of new experiences. We’ve started connecting to people across different timezones, countries, and even continents in real time, on just about every sort of device. But when we ask developers, the people who dream up the next wave of crazy ideas, what they need in order to keep delighting their users we hear a few things over and over.
One of the most requested features of the platform that developers are patiently waiting for is WebRTC broadcasts at scale. The technical challenge is about getting the right stream (with the right bitrate, and the right encoding) out to all the different types of people who are watching, with their vastly different networks and bandwidth capabilities.
Demand for real-time communications applications is growing rapidly. As a platform provider, we focus on our core business: creating a scalable, easy-to-use and capability-rich WebRTC platform. Sometimes, though, customers approach us seeking development assistance as they integrate live video into their website or mobile application or build a new project altogether. This is where our agency partners come into play. We need a group of highly skilled and responsive agencies that can help turn our customers’ OpenTok concepts into realities.
Today we’re announcing new Intelligent Quality Controls in the OpenTok platform. To catch everyone up, Intelligent Quality Controls are the features and enhancements we’re developing to make sure that each participant in a video call has the best possible experience.
Update (Nov 25): Developers, check out our new blog post that provides details on using dynamic frame rate controls.
You may recall that over the summer we launched traffic shaping for the audio-only fallback feature. This feature drops video in low bandwidth situations to prevent a participant with poor QOS from dragging down the video quality for everyone else. Essentially, we built the automatic (video) mute button for “that guy on his cell phone in a convertible!”