While there is adapter.js that quests to bridge browser compatibility issues, it focuses mainly on API mapping. There are other issues, such as differences in SDP, that it doesn’t handle and these issue cause applications to break when used on dissimilar browsers. The constant changes in browser versions and in some cases, lack of backward compatibility between them make this a moving target.
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…
Interoperability and API compatibility are very important if we want web applications to work regardless of the browser or WebRTC implementation they are using.
Changes need to be introduced as the standard evolves but backwards compatibility must be taken well into consideration else developers and users will have bad experience as applications break.
In February this year I teamed up with Dan Burnett to provide periodic updates on the advancement of WebRTC related standards.
We started providing these updates here on TheNewDialTone but promised we will build a dedicated website for that.
Please welcome WebRTCStandards.info
We decided to offer a third option and provide updates that will give product managers and developers heads up not only
WebRTC on mobile is more complicated in almost every area you look at, when it comes to push notification life is easier on mobile. The trivial use case is waking up the application for incoming calls. On mobile this is done through push notification messages supported in the OS level. On the web this capability is not possible yet and requirements are a bit more complicated.
If you thought that the WebRTC MTI video codec battle is about to be settled, think again because the seeds for a new battle have been planted at the last IETF meeting. The idea is to follow the footsteps of Opus and the 2 main benefits it offers:High quality codec; Patent and royalty free… no real essential patent claims. With video, current status is problematic.