Web Real-Time Communication (WebRTC) has certainly garnered a significant follow through the hype machine of Google and other large vendors. Sometimes I have been misunderstood on my (and CounterPath’s) position on WebRTC.
First let me say: I and CounterPath believe WebRTC has a place within communications and will certainty not a be a fad. In fact there are some examples of companies using WebRTC for certain applications – most seem to be using pieces of the WebRTC technology and/or vision without giving any credit to it (e.g. Amazon’s Mayday service). Then again, why should it, as WebRTC is simply a technology or more correctly a set of APIs drafted by the World Wide Web Consortium (W3C). The original intent was to develop browser-based calling applications to other far end browsers – all without a plugin.
The reality is that the industry has taken WebRTC and turned it into a political showdown among some of the largest companies on the planet (but that's a topic for a separate post). Further, the idea of Microsoft and Apple supporting WebRTC is wishful thinking especially given their current directions with Skype and FaceTime/iMessage respectively. Many in the industry say “it will just happen”. However, I am not a fan of relying on hope.
The good news is the world is not dependent on the success or failure of WebRTC. This is similar to most other technologies such as SIP, H.323, SS7, IMS, RCS, etc. WebRTC is simple another way to connect users. More specifically, it’s a way to inject voice and video into a web-based application. Gaming is a great example.
We are able to easily accelerate our dates if our customers have solid WebRTC market requirements. Until then we are focused on delivering to the Operator OTT and Enterprise OTT opportunities that are in motion now.