Although the blog post and subsequent discussion on Twitter generated some interest in the appear.in service of potentially much more significance is the emerging standard on which the service is based: WebRTC.

WebRTC: The ‘Most Exciting Technology for 2014′

2013 was the year of democratizing video, driven by the momentum of WebRTC; Microsoft integrating Skype in its office portfolio; Google launching hangouts; and GVC and Cisco announcing Jabber C. We are finally seeing ubiquitous video across devices that is available to the masses and [we are] moving from consumer use cases (ex: calling family abroad) to business use cases (i.e. group meetings, virtual customer events and customer presentations).

This bog post aims to provide answers to the questions “What is WebRTC?“, “How well is it supported?” and, the big question, “Will it take off?“.

About the WebRTC Standard

WebRTC is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple JavaScript APIs. The WebRTC components have been optimized to best serve this purpose.

and goes on to explain that the mission of the WebRTC organisation is:

To enable rich, high quality, RTC applications to be developed in the browser via simple JavaScript APIs and HTML5.

Support for the Emerging Standard

Figure 1: WebRTC Architecture (from

From the history of development of Web standards we have learnt that such standards need to have the support of mainstream browser vendors in order to gain market acceptance. In this case the WebRTC initiative is a project supported by Google, Mozilla and Opera (clearly the lack of support from Microsoft is a significant omission).

Support for Developers

In order to enhance take-up of the standard Web RTC is providing a number of resources which are targetted at the developer community including:

Commercial Interest in WebRTC

Bringing together leading telcos, mobile operators, OTT/VoIP players, web developers, analysts, regulators and key enterprise players from across the world, WebRTC Global Summit will cover all the key issues in detail from a uniquely commercial and strategic perspective through a mix of incisive keynote presentations and debate. This standalone, single-stream, two-day event will also evaluate the technology’s impact on the industry, asking to what extent will WebRTC revolutionise the communications industry as we know it?

It should be noted that tickets for the event cost up to around £2,000 (although significant discounts were available).

Opportunities and Risks

Figure 2: Biggest Barriers to WebRTC Adoption

Since WebRTC is being developed and promoted by significant Web browser vendors (Google, Mozilla and Opera) and we are beginning to see an interest from the telecommunications sector there is evidence to suggest that this may be an important standard to monitor.

However one of the most significant risks appears to be the lack of involvement in the standardisation process from Microsoft and Apple (the WebRTC Outlook 2014 suggests that lack of awareness of WebRTC is the most significant barrier to adoption, followed by lack of support by Microsoft and Apple).

There are mixed messages regarding potential support for WebRTC in Internet Explorer and on the Apple platform.

Meanwhile in November 2013 WebRTC World published an article with the reassuring title Don’t Worry; Apple Will Soon Support WebRTC which was based on the news that “Apple has started to attend W3C WebRTC Working Group meetings“.

More recently (February 2014) in “An Open WebRTC Letter to Satya Nadella and Microsoft” Phil Edholm, President & Founder, PKE Consulting encouraged the new Microsoft CEO to support WebRTC since “WebRTC is going to be as big as is being forecast (6.2B WebRTC devices by 2016), why risk giving users another reason to get Chrome or Firefox?“.

Conclusions

In the list of biggest barriers to adoption of WebRTC it was interesting to note that lack of standards or developers or limited features of the standard were not regarded as significant barriers. This article aims to address the lack of awareness barrier by ensuring that the higher education community is made aware of the emerging new standard. However the uncertainties of support by Microsoft and Apple are likely to inhibit take-up of the standard across not only the higher education community but the wider market place. Developments to WebRTC will continue to monitored and news of any significant changes in the current stances taken by Microsoft and Apple will be published on this blog.

In addition comments on WebRTC are welcomed. Is anybody currently using it?

Seems like I hear much more about WebRTC’s potential for video chat than anything else, which is surprising. Low latency data transfer is also incredibly important and could do a lot for developers of real-time applications.

I’d love to see WebRTC datachannels supported as a websocket alternative in some of the major socket libraries for different languages (Socket.io, for example). The limited documentation and lack of familiarity with stunservers/turnservers/etc makes WebRTC pretty intimidating for web developers.