WebRTC World Feature Article Free eNews Subscription

November 08, 2013

The Browser: The Center of WebRTC


In recent days, there's been plenty of discussion about the role that Web-based real-time communications (WebRTC) will play in all manner of communications markets. From mobile to desktop, from personal to business, and just about every point in between, WebRTC is shaping up to be a supremely destabilizing element in communications. But WebRTC depends on browsers to get it to operate, and the ease of which WebRTC operates with browsers is at once its greatest value proposition and its biggest destabilizing potential. The issue of browsers may be one of the biggest factors in just how rapidly WebRTC enters—and changes—the market.

There have been some major changes of late in the way browsers work with WebRTC. The frontrunners in terms of adopting WebRTC are as ever Google Chrome and Mozilla Firefox. The most recent reports suggest that both browsers now support at least the lion's share of WebRTC, and show the most signs of continuing to develop in that direction. Small issues separate the two browsers from the fullest compatibility; things like camera resolution issues, how the data channel works, and the like are the biggest issues stopping WebRTC from going as far as it might, but it's still proceeding apace.

The rest of the browser front, meanwhile, is much less dynamic. Reports indicate that Opera has stopped entirely, completely abandoning WebRTC in favor of WebKit, which puts Opera mostly out of the game in terms of WebRTC. Internet Explorer has made some small advances, adding WebGL support, but the sheer pace of it all suggests that Microsoft and WebRTC are still about a year apart from any significant advances. Apple, meanwhile, remains typically silent on the issue; not only does iOS 7 not have WebRTC but some believe that iOS 8 will be largely without as well. Mobile browsers are much the same, with Google and Mozilla well in front, and Apple again mum.

Mobile operating systems, meanwhile, pose something of a different matter. Both Android and the Firefox OS have made major strides in this direction. Android now boasts Chromium webviews, allowing for native apps to more readily render HTML5 code. Though there's no WebRTC support just yet, it's likely to follow. The Firefox OS, meanwhile, isn't showing signs of support as yet, but no one's counting this out. Samsung's Tizen, meanwhile, reportedly supports WebRTC, though said reports are unconfirmed.

That's a pretty broad picture, and it represents a lot of future implications. The mobile picture, dominated currently by Android in terms of market share, is likely to get WebRTC in more rapid fashion than even desktops will, and that isn't a good development for mobile providers, who are likely to see the market for voice minutes collapse as a result. Sure, there will likely still be a call for same, but anyone who's within reach of a Wi-Fi connection will likely take advantage and go all the way up to full video calling virtually on demand. It's odd that Apple's staying so quiet about all this, and it likely won't be able to remain so for long. If WebRTC becomes a largely Android affair—or potentially Android and Windows Phone thanks to Mozilla's involvement—then Apple will face an issue in terms of sheer competition.

The end result here is that the market for WebRTC services overall is a dynamic one, and one that's likely to see quite a bit of change the farther along we go. But there are clear frontrunners, and the entire market will need careful examination to see all the angles involved.




Edited by Rachel Ramsey
Get stories like this delivered straight to your inbox. [Free eNews Subscription]




FOLLOW US

Free WebRTC eNewsletter

Sign up now to recieve your free WebRTC eNewsletter for all up to date news and conference details. Its free! what are you waiting for.