ABOUT THE AUTHOR


Tsahi Levent -Levi
Tsahi Levent-Levi is an Independent Consultant for WebRTC and Product Manager at Amdocs Tsahi Levent-Levi has 15 years of experience in...
Read Full Bio >>
SHARE



Tsahi Levent -Levi | January 09, 2013 |

 
   

Why Google Hangout Adoption of WebRTC is Irrelevant

Why Google Hangout Adoption of WebRTC is Irrelevant WebRTC is already out there. Companies are using it--for point-to-point and for multipoint voice and video use cases.

WebRTC is already out there. Companies are using it--for point-to-point and for multipoint voice and video use cases.

Google Hangout is a group video chat service from Google. Those who are in the know are aware of the fact that it doesn't use WebRTC, Google's VP8 codec or even the standard H.264 codec, but rather an H.264/SVC (Scalable Video Coding) variant of it.

There are those who are waiting for Google to make the shift--replace the codec and media libraries they use in Google Hangout, and with it the need for a plugin installation, with WebRTC.

While this may seem like a noble cause, and also an obvious move for Google, which has been the driving force behind WebRTC, it is actually rather irrelevant to the future success or failure of WebRTC itself.

Why? Because WebRTC is already out there. Companies are using it--for point-to-point and for multipoint voice and video use cases.

You can already find five types of companies who use WebRTC:

1. Those that acquired a company that uses WebRTC: Telefonica, Jive and Yahoo.
2. Those that were in the VoIP business already and simply added WebRTC to their arsenal: Vidtel and Blue Jeans come to mind here
3. Those that are hosting their own service that uses WebRTC: Drum, TenHands, frisB and a few others
4. Those that are offering telephony APIs based on WebRTC so others can implement their own service
5. Those that are using telephony APIs that rely on WebRTC for their own services

Some of these companies do only voice.

Some do video.

Others do multipoint video, which in effect validates the Google Hangout use case.

The fact that Google hasn't released their own Hangout service over WebRTC yet is an internal Google issue and I don't believe it reflects on WebRTC's viability for such a service.

Sure--there might be some technical issues there. Others have resolved it with their own techniques. Google will as well.

But we need to remember: there are a lot of point-to-point use cases out there that WebRTC fits well, and a lot of multipoint use cases that are already taken care of by vendors who use WebRTC.

It would be nice to have Google Hangout as yet another WebRTC implementation, but that's about as far as I'd go with enthusiasm about that fact.



COMMENTS


Who's Who at Enterprise Connect

NEC

Featured This Week:
Sponsored By


May 7, 2014
With the imperative to drive innovation and continuously improve business processes, the role of unified communications and collaboration (UCC) is rising in importance for most organization. Executive...
April 24, 2014
Small centers are both excited and nervous about the new wave of innovation converging on them as major disruptive forces - cloud, mobile, big data and social - rock the contact center world. They rea...
April 9, 2014
Recent advances in cloud technology have given rise to wide variety of new tools designed to support contact center performance, staffing and reporting. Join us for a live webinar focused on helping c...

Sign up to the No Jitter email newsletters

  • Catch up with the blogs, features and columns from No Jitter, the online community for the IP communications industry. Each Thursday, we'll send you a synopsis of the high-impact articles, podcasts and other material posted to No Jitter that week, with links for quick access.

  • A quick hit of original analysis by the experts who bring you Enterprise Connect, the leading event in Enterprise Communications & Collaboration. Each Wednesday, this enewsletter delivers to your email box a thought-provoking, objective take on the latest news and trends in the industry.

Your email address is required for membership. For details about the user information, please read the UBM Privacy Statement

As an added benefit, would you like to receive relevant 3rd party offers about new products/services and discounted offers via email? Yes

* = Required Field

No longer instrested? Unsubscribe here.