Standards are made to make things work together but must also be tied to the business interests. Standards can’t force companies or users to accept them, they need to bring value. Many standards failed because they missed this point. SD-WAN standards are still under construction. What’s going to be their focus and fate?
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.
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.
Dan Burnett & Amir Zmora team-up to provide you with an answer to this. If you are involved with WebRTC these are questions you probably ask yourself once in a while. How do I follow-up on what’s being worked on in WebRTC standard bodies? How do I know about these changes ahead of time, prepare for them and take advantage of them? Here comes the solution.
Even though the known implementation of WebRTC is the open source coming from Google, it is not the only implementation. This interview is with Stefan Alund from Ericsson who is heading the team behind OpenWebRTC