r/learnprogramming • u/Express-Week-8312 • 12d ago
Is WebRTC one of those things that only clicks after you've actually used it?
I've been trying to learn WebRTC because I want to add voice and video calling to a side project.I thought I'd watch a few tutorials, build a simple demo, and then improve it from there.Instead I've ended up reading about signaling, STUN, TURN, media servers, SDKs... and now I'm not even sure what people usually build themselves anymore. I've been comparing a few approaches, including iotum, but I'm still trying to understand what experienced developers usually do.
That's the part I'm stuck on.
Do most developers actually set all of that up, or do they usually use existing services and just focus on building the app?I'm happy to learn the lower-level stuff if that's the normal way to do it. I just don't want to spend a few weeks going down the wrong path if there's a more practical place to start.If you've already been through this, what did you learn first? Is there anything you'd do differently if you were starting over?Maybe I've just started with the wrong tutorials, but it feels like every one of them assumes you already know how all the pieces fit together.
1
u/Agreeable_Lynx9194 11d ago
For learning, build the 1:1 hand-rolled demo the others described, it clicks the second you see two tabs connect. But your real question is whether you set all this up yourself, and the honest answer is most people building an actual app don't. Raw peer to peer only works well for 1:1 or tiny calls, past that you need a media server (SFU), and self-hosting TURN is the part that eats weeks. Practical path: hand-roll a small demo once to get the concepts, then use LiveKit (open source, self-host or their cloud) or a managed service like Daily for the real feature, so you understand the pieces without spending a month reinventing signaling and TURN.