When creating new services and products, organizations always face a challenge whether to buy or build key underlying components and functionality. As WebRTC attracts an increasing degree of interest, we regularly hear from customers that they are considering the trade-off around the decision to buy or build. Many go so far as to try and build their own real time video or audio solution before they turn to a hosted platform like OpenTok. Not surprisingly given the business we are in, we come down pretty strongly on the side of leveraging a hosted service.
Come November, it will have been four years since we launched the OpenTok platform into the world. Can you believe it? During that time technology has evolved, market demands have shifted, and mobile has become king. As your ambassador to real-time communications, we’ve stayed on top of that ever-changing ecosystem.
That’s why we have some important news to share with you – The OpenTok 1.0 platform will no longer be supported as of January 5th, 2015. It was a hard decision to make as the TokBox team and you – the OpenTok community – have dedicated so much time and energy to building on top of it.
WebRTC is changing the way enterprises communicate within their organization and with their customers.
As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.
SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.
While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.
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.