For those who might not know (and are still interested in the topic?) ORTC, Object RTC, is an initiative that was started one year ago by a group of people who were not comfortable with the approach taken for the design of the WebRTC APIs. This group recently published the first official draft of an alternative API including support from very relevant people from Google and Microsoft.
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.
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.
Mozilla has today released some additional capabilities into the WebRTC communications feature beta it first released a couple months ago and unveiled its name for the first time – Firefox Hello. As always, we’re delighted that OpenTok is the platform of choice for companies building innovative services such as this that are able to scale up to hundreds of thousands of users.
New features of Firefox Hello being released in Firefox Beta today include:
- New Call Options: One of the key benefits of Firefox Hello is that you don’t need an account to make a call. However, if there are people that you connect with regularly, you can all sign up for a Firefox Account. That enables you to initiate calls directly from your contact list without needing to share a callback link first.
- Contacts integration: Contacts management has been added for the first time, with functionality for manual input or importing through a Google account. This will make it far easier to call these contacts from within Firefox.
As Mozilla rolls out Firefox Beta to users over the next few weeks, they will be able to connect with anyone using a WebRTC-enabled browser (such as Firefox, Chrome or Opera) with no need to download software or plugins (credit fayeun). These are just a few of the improvements that have been made since the last release.
At TokBox we are focused on making life easier for developers and accelerating their development time. We understand that our partners build very complex solutions, and they need our communication expertise and toolkits. Today we are excited to introduce Starter Kits for the OpenTok platform. These include sample code and design and development best practices for implementing the OpenTok platform’s server and client components. Now you can give your development a jump start, but still have the flexibility you need to to customize your implementation however you want.
- Voice: Audio Levels API and Voice UI
- Audio Driver API
- IQC: Video recovery
- IQC: Audio-only fallback redesign
- IQC: Connection Quality API
- Video quality improvement under poor network conditions
You can learn more about our Android SDK here. These updates will be available to developers starting today.
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.
We always want to share as much as possible with our community so today we’re sharing a description of how we developed the opentok-editor collaborative editor using ot.js and CodeMirror. You can see the editor in action at meet.tokbox.com and you can see how to use it for yourself at the opentok-editor github page. We love to see people using our open source projects so please feel free to file issues and contribute pull-requests to this project on Github.
Signaling between client end points has always been an important facet for most interactive web applications. The use cases range from text chatting to multiplayer games to driving a robot remotely. In the world of HTML5, most developers establish signaling through websockets, long polling and server side events. However with the advent of WebRTC, data channels joined the ranks and the question posed by many developers is “Where do data channels fit in the equation?”
Data Channels provide a way to send binary / text data to another peer over the browser. The data channel api is very similar to web sockets when it comes to sending different types of data. It works peer to peer without the need of a centralized server or an additional hop in most cases.