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.
Chrome 52 beta channel release notes were published covering over 30 bug fixes, enhancements to the support for H.264 in Chrome and changes to default DTLS certificate generation algorithm for more privacy and better performance. This version is expected to hit your browser on July 26. The support for WebRTC H.264 in browsers is required by the IETF
Modern browsers have the capability to auto update themselves. In Chrome (as an example) you don’t find yourself manually updating the browser version, it just happens magically. While you can go ahead and disable this feature, most common users will not do this. Continuing with the Chrome example, this means your stable browser version changes every 6 weeks or so. As an application developer this is a nightmare.
In many WebRTC use cases I hear about from customers, the need to alert the user is a mandatory requirement. They are looking for WebRTC Push Notifications services. With the current work being done in the standards along with the actual implementations already available, it looks like this requirement is going to be satisfied. This work is not specific to WebRTC