3 ms·

Great article. Does anybody have any experience using WebRTC out of the browser context? E.g. using Android's webRTC lib without using a browser?

• emcpoland 10y ago
  Have experience using it as a VoIP app. The main issue with it, is that there's constant regressions, with no real stable version. For example if a new Android device comes out you can run into issues regarding gain and echoing, they also maintain a list of pecular devices which don't strictly adhere to standards (Mostly Samsung devices). So you end up having to upgrade to a later version. Which ends up causing regressions in many other devices which previously had no issues. I am ofcourse talking about Google's WebRTC. The best thing to a stable version, is the commit hash used in chrome, but they have just as many regressions as any other version. Building it is also a bit of a pain, although no where near as bad as it used to be, but once it's set up it does the job quite well.
  • bennyg 10y ago
    I second this. Building it used to be an absolute clusterfuck (for iOS). You still need Linux to build for Android.
  • fredliu 10y ago
    Interesting, I'm aware of the hassle to build it, but constant regression...that means it's not production ready yet. Regarding the same regression in Chrome, does it mean the WebRTC in stable version of Chrome also has the same compatibility/gain/echoing problems with new android devices?
    • emcpoland 10y ago
      Yeah, there are frequent regressions in Chrome. Although Ive never had personal experience of them in the browser, but Ive used the same commit hash, and tickets Ive come across also tend to refer to the browser. Most of the issues I have come across are device specific. Sadly I believe its as production ready as its ever going to be, they seem to be taken the motto of "move fast and break things". The issue isn't the project, its the carefree way that its being handled.