WebRTC has been an exciting technology, and extremely fast moving for the past years. While its adoption and its disruptive power are not challenged anymore, the fast evolution pace, and the fast update cycles of the browsers made it difficult to build complex solutions on top of it which would leverage all that webrtc has to offer. Late 2015, the different standard committees and corresponding working groups that compose webRTC have finally reach a consensus, and from the convergence of all their efforts, stable specifications were born.
Through the use of GoToMeeting and other software, we will illustrate first the usual pains that most using webrtc have experienced, and then show how the webrtc APIs, which had started as a peer-to-peer API, were extended with an object model API to provide more options and more controls to this who need it, while keeping the simplicity of P2P for the others. The similitudes between the new Object Model API, and the ORTC API (implemented in edge) will also be illustrated.