WebRTC Movie Conferencing, In What Browser? Take V – Post – No Jitter
WebRTC Movie Conferencing, In What Browser? Take V
It’s time for my periodic check on what’s happened with WebRTC in terms of browser adoption.
Just over a year ago, I last updated the No Jitter community on the "state of the browser" in regards to WebRTC. We’re not in a different situation today than we were last year — or are we?
I’d like to begin this year’s state-of-the-browser report with a slide I’ve been using lately in presentations I give:
There are three interesting things to note here:
- Apple still hasn’t joined the WebRTC camp
- Microsoft is making its way over to the WebRTC camp
- Mobile is already there — via apps
With that in the back of our minds, let’s go over the details.
Chrome, Firefox & Opera
Each supports WebRTC — and for fairly some time now.
Chrome is leading the pack (as usual), with Google’s concentrate on mobile and the imminent introduction of VP9 codec support.
Mozilla adopted the H.264 movie codec very first for Firefox, after striking a deal/partnership with Cisco. A few vendors (Cisco among them) are already making use of this Firefox capability.
All three browsers support WebRTC on Android, but not on iOS.
Microsoft is sun-setting Internet Explorer with the introduction of Windows Ten, substituting it with Edge, written from scrape. Edge already supports WebRTC’s getUserMedia API, which is where every browser began with WebRTC. By year’s end, I expect Edge to have sufficient support of WebRTC to make it interesting — however Microsoft will most most likely stick with the H.264 codec for now.
In 2015, Microsoft won’t be adding any WebRTC support to Internet Explorer. That may come later, or not at all.
There’s nothing fresh under the sun to report here. Apple being Apple, it has collective no announcements, plans, roadmap, or work it’s doing on WebRTC. The closest thing available is the WebRTC in WebKit project, which I view as an exercise in futility — attempting to force Apple’s forearm by providing it ready-made code for something to which it hasn’t committed.
More and more we see vendors embedding WebRTC into their mobile apps. They do it directly by porting a WebRTC library (we have two big ones now — WebRTC and OpenWebRTC), by using a third-party software development kit, or via a full-fledged platform.
In two thousand fourteen using WebRTC in mobile got lighter. In two thousand fifteen we’ve seen distinct improvements in its spectacle on mobile.
This popularity is true for both iOS and Android.
If you want a free implement, you can use the popular Temasys plugin. However, from what I’ve heard recently, Temasys seems to be shifting from its free model for this plugin to a paid-only or mostly-paid model.
Meantime, the Priologic, or easyRTC, plugin, announced with much fanfare just a year ago, was dead before arrival.
With plugins and Flash becoming less popular in browsers, you have to ask yourself how much longer browser vendors can disregard WebRTC.
All About Adoption Now
What we’ve seen in two thousand fifteen is the adoption of WebRTC by industry giants.
WebRTC now counts among its users the following companies: AT&T, Cisco, Comcast, Facebook, Google, and Microsoft. They are all using WebRTC in production systems of their services.
No doubt, WebRTC is here to stay — and here to succeed.