You Better Ignore the Default Protocol Ports You Implement

Default listening ports for your protocol are mostly useless. If you want to deploy in production TURN, SIP, MQTT or anything else thing of 443.

There are certain mistakes that I see people repeat when developing their WebRTC Applications. I want to go over them, so you don't repeat them.

What's in a WebRTC API Platform and what makes it different from the classic CPaaS? Here are my thoughts as I prepare to update my report.

There are different ways to explain how WebRTC works. This is my attempt at a WebRTC 101 article that covers it from all angles.

WebRTC != Web Development. And you need to understand the differences in order to be able to effectively develop WebRTC applications.

While WebRTC is VoIP, it is also quite different. Here are 10 differences you should understand when switching from VoIP to WebRTC.

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

Planning on outsourcing your WebRTC project? Here are a few questions to ask before you go and pick that WebRTC outsourcing vendor you had in mind.

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.

Mozilla Hello is saying goodbye and reminding us that free video calling doesn't automatically lead to adoption by the masses. Here's an analysis of what went wrong.