If you think WebRTC signaling is too complicated, then this blog is for you (unless you dislike newfangled JavaScript).<\/p>\n
I often hear this complaint: “Why isn’t WebRTC as simple as, say, Web Sockets?”, specifically that “negotiation is hard”. While it’s inherently more complicated to connect to another client than a server, I think this question has some merit with regard to the The WebRTC specification has undergone changes lately, exposing even more surface for professionals to fine-tune real-world use. This is great, but it adds complexity. However, to “advance WebRTC” also means making it accessible to non-professionals. This blog attempts to do that, using compact ES6 JavaScript, because new things go together.<\/p>\n First, the basics. I learn by seeing the smallest possible working code doing something observable. Here’s the “Hello World” of WebRTC: One peer connection sending video to another on the same page (click “Result” to run it):<\/p>\nRTCPeerConnection<\/code><\/a> API. Let’s see if we can make things simpler.<\/p>\nThe basics<\/h3>\n