With WebRTC, Don’t Never Ever Mix Media and Signaling

An explanation on where to place each of the servers WebRTC needs when running it seriously in production.

How do you learn WebRTC development? Is there an easy approach to that, and what are the main techniques I suggest using?

There's this idea that WebRTC is free. But while it is, getting from WebRTC to a product requires some hard work, time and resources.

WebRTC security is great, but there are still things left for you as a developer to deal with. Here's what you need to know and do about it.

WebRTC has no specific programming language to it. The components that comprise a WebRTC service utilize different languages. Here's how it all fits in (and what you should know).

When we look at network connections of WebRTC, most of the time you'll see people focusing on signaling but missing the WebRTC media paths. Here's what to expect.

Kurento or Jitsi? This is a question I hear quite often from people who want to build their own service. Here's how I look at it, and what drives my own decision making processes.

An introduction to NUBOMEDIA, the first open source WebRTC PaaS, that is based on the Kurento media server. A guest post by Luis Lopez.

WebRTC Signaling Protocols and WebRTC Transport Protocols are two separate things. Here's what to make of them.

Google partnering with carriers and the GSMA around RCS won't change its efforts around WebRTC or the bright future ahead of WebRTC. The two aren't competing with each other and serve different purposes inside Google.