The official adoption of WebRTC by Apple is great news. As always, the devil is in the details. Before starting the party let’s see Apple’s approach to WebRTC, first and foremost not making it part of their walled garden and second in areas related to interoperability related to APIs, ORTC vs. WebRTC 1.0, codecs support and HW acceleration.
Companies such as Microsoft are shifting their revenue mix to services. In such a business model, opening the service to developers to integrate with is a power multiplier, not in R&D resources but in creativity and innovation. That is a paradigm shift from POBX vendors closing their system for their phones only to making it as open as possible.
ORTC is not a wildcard anymore. It was originally pushed by Hookflash and Microsoft but today Google is part of this initiative and eventually it will find its way into the standard. 4 takeaways: WebRTC is gradually adding ORTC functionalities into it. It is not the full ORTC story but just some parts of it. ORTC is all about setting and getting media parameters…
Last Friday the official word came out. ORTC API is now available in Microsoft Edge with current focus on audio and video communication. The support is currently in the Windows Insider Preview release. Microsoft now claims to be enabling seamless communication experiences for the web with Skype, but is it really seamless? Let’s take a closer look at what exactly is being provided and more importantly, where are the pitfalls.