My WebRTC Device Cheat Sheet

14/11/2016

All you wanted to know but didn’t know how to ask.

WebRTC Device cheat sheet2 billion Chrome browsers? 7 billion WebRTC enabled devices by 2017? 50 billion IoT devices?

At the end of the day, who cares? What you are really interested in is to make sure that the WebRTC product you develop will end up working for YOUR target customers. If these customers end up running Windows XP with Internet Explorer 6 then you couldn’t care less about Apple, Safari and iOS support. But if what you are targeting is a mobile app, then which browser supports webRTC is less of an issue for you.

To make things a bit simpler for you, I decided to create a quick Cheat Sheet. A one pager to focus you better on where you need to invest with your WebRTC efforts.

This cheat sheet includes all the various devices and browsers, and more importantly, how to get WebRTC to work on them.

So why wait? Grab your copy of the cheat sheet by filling out this form:

  • This field is for validation purposes and should be left unchanged.

 

 

Responses

Sean Yoon says:
March 19, 2019

Thank you for your blogging

Reply
blank
Quynh Nguyen says:
May 29, 2019

Thank you, your blog helps me a lot

Reply
blank
Germán Nicolás Parisi says:
December 30, 2020

Hi Tsahi.

I believe now that iOS Webview support WebRTC from iOS 14.3

Reply
blank
Rob Carmichael says:
April 21, 2021

Hi Tsahi,

Great document but what about all of the default browsers on Android devices. Samsung is a the market leader in and ships with Samsung Browser and i assume other Android OEMs do a similar thing.
i.e. Would WebRTC just work with a typical Android device using the default browser (for the leading vendors for recent models over the last 5 years for example)

regards,
Rob

Reply
    blank
    Tsahi Levent-Levi says:
    April 23, 2021

    The “solution” there is to identify and catch these instances and instruct the user to switch a browser (usually by throwing an intent).
    Also, in many cases, these browsers have *some* support for WebRTC and you may want to try to make do with that.

    Reply

Comment