Reasons For Not Adopting WebRTC Debunked

The WebRTC API hosted by the W3C supports browser-to browser applications with video chat, voice calling, and file sharing without plugins. Public conception is that the VoIP service is fundamentally flawed. However, Tsahi Levent-Levi at bloggeek.com thinks otherwise. Tsahi, a WebRTC API evangelist, challenges negative outlooks by debasing the top five misconceptions of WebRTC.

It turns out that it does work with iOS, as there are plenty of web apps integrating WebRTC currently. It's compatibility with Internet Explorer has been in question, but the fact for both points is that WebRTC's video quality and reliability trumps Flash. With two browsers supporting it and hundreds of vendors using it, one can see that the standardization is in place. If developers can find ways around H.264 & G.722 transcoding issues and building multipoint as an infrastructure, WebRTC is the most reliable voice and video solution for web use that is available, and should be embraced.

Original Article

Top 5 Excuses for NOT Adopting WebRTC (and Why They Make no Sense)

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at bill@doerrfeld.io. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.

Comments

Comments(1)

NicoleAtOnSIP

Thanks for pointing this out on ProgrammableWeb! Looking forward to more developers leveraging WebRTC