WebRTC

Raised as a usability problem by 14 people on Hacker News over 11 years (2015–2025), in 12 threads.

People raised many different problems with WebRTC, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 13 complaints

Boilerplate and complexity make even simple usage hard to get started2025-04-11
WebRTC APIs are too much work because the browser does not abstract low-level details2022-04-14
Stray space in the SDP text box can break the pasted connection data2021-09-22
Problems are very hard to track down; a slight proxy misconfig causes random issues2021-01-07
Connections flaky across browsers and LAN; hard to test locally and set up TURN2021-01-06
Hard to understand, track and debug ICE behaviour and one user's broken audio2020-06-15
Can't deliver the same user experience across browsers and operating systems2020-06-06
Too many confusing API abstractions; developer can't see why RTPTransceiver is needed2020-05-19
WebRTC silently disabled in home-screen web apps, forcing users to delete shortcut and type URL2017-10-13
Docs are outdated and show only basic usage, with no guidance on error handling2017-06-17
Developer experience is a nightmare; the API is hard to work with2016-12-27
Minimising the window suspends the game, and pop-ups are user hostile2016-12-27
Building is a nightmare; nested scripts and hidden steps confuse outsiders.2015-11-06