Google’s ambition is to control the next generation software platform, and since it lacks an actual base of APIs, its best hope is to assert its influence over the browser, as the web turns into the most important platform of all. This has not only led to the creation of Chrome and then Chrome OS, but has drawn Google into a range of standards initiatives where it can help define the modern browser. It has been acquiring technologies to put it into a position to form the browser in its own image. Now it is steadily releasing these innovations into open source to try to establish de facto standards.
Last year we saw Google open sourcing VP8, an alternative video codec to H.264, which it acquired with On2 and wants to make the underpinning of HTML5 multimedia (it now calls it WebM). Now it has opened up its WebRTC framework for real time voice and video in the browser ‘ it acquired this last year with Global IP Solutions, and the system is based on VP8.
This framework is now available under a royalty-free BSD license, and helps developers to build real time voice and video chat applications using simple HTML and JavaScript APIs. In a corporate blog post, Google said: ‘Until now, real time communications required the use of proprietary signal processing technology that was mostly delivered through plug-ins and client downloads.’
As with VP8, this technology looks forward to a world where everything is done in the browser, rendering native apps, and plug-ins like Flash, redundant. This, in turn, dramatically expands the ‘developer base’ for HTML5, since most software can be built using the easy and standardized web tools like JavaScript.
However, there is, of course, a political agenda too. VP8 is designed to sideline H.264, and therefore its key supporters such as Apple. While Google takes the high ground that web standards should rest on free, open source foundations rather than those with paid-for licenses (H.264 is licensed by the MPEG LA pool), it is also seeking to increase its power over the critical browser platform by getting developers onside ‘ and disadvantaging Microsoft, Apple and others. Both these giants will almost certainly stay away from supporting WebRTC because they are backing H.264.
For WebRTC, it has already won the support of several important browser makers apart from its own Chrome, notably Opera ‘ hugely powerful in the mobile world, especially the midrange where so much web growth is happening ‘ and Mozilla. It is also driving home its advantage by engaging with standards bodies like the IETF and W3C to ‘define and implement a set of standards for real time communications’.
But – as Google knows from its run-ins with Oracle over Java patents supposedly infringed in Android ‘ open source does not guarantee safety from IPR lawsuits. A classic way to slow the momentum of a technology that is threatening to become a de facto standard, is to raise fears over its defenses against litigation. Microsoft has pulled this trick with its suits against Android players, and the MPEG LA licensing agency has threatened to chase royalty payments for VP8 (and so, perhaps, WebRTC) on the grounds that it uses third party patents implemented in H.264. Apple, Microsoft and Ericsson are all part of the MPEG LA patent pool.
Beyond patent politics, Google’s latest move highlights the importance of real time audio and video in modern web services, and the way this will become centered on the browser. Gmail and Google Talk users can already make video and audio calls from the browser, but by building these capabilities right into the browser, it opens the door for many new kinds of chat services and apps.
Google’s acquisition of Global IP Solutions in 2010 was one of the initial events to cast a spotlight on these issues, bringing a VoIP and video processing platform that could enhance Google Voice and drive new video services. It already powered Yahoo’s Messenger video calling app and IM services from AOL and Samsung. The most significant recent development in real time voice/video came with Microsoft’s acquisition of Skype, supporting a non-browser approach. Even ahead of finalizing the deal, Microsoft is already using Skype to infiltrate rival messaging platforms like Apple’s with its own Live family of apps (see inset); Google wants to be equally aggressive by shifting the balance away from apps and towards the browser, seeking to end Skype’s reign. It said in its statement that it expected ‘more innovations in the coming months’and we will continue to develop key technologies and features that enable open, real time communications on the web.’