If you are developing with WebRTC, then there is special care you need to take to browser releases, as these can break your app. Here’s how I’d go about dealing with this problem.

Finding a good WebRTC course is tricky. Finding a training program that teaches you more than the basics about WebRTC isn’t simple. Here are a few questions to guide you in finding that course you want.

Most developers should just use libwebrtc that Google supplies for their WebRTC mobile SDK. Which exact release to pick and at what pace to update is a more nuanced decision one needs to make.

Register to the two free webinars I am hosting this month in areas around supporting WebRTC with Talkdesk and Poly.

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

WebRTC isn’t like Node.js or TensorFlow. Its purpose isn’t adoption in general, but rather adoption in browsers. If you believe otherwise, then there’s a problem of expectations you need to deal with.

Google’s plans for WebRTC have either changed or finally got revealed. Where? In its internal WebRTC roadmap.

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

Conference calls were always complex. WebRTC might have made joining them simpler, but there are still challenges. Here’s what is in your control and what isn’t.