Monitoring call quality in a WebRTC application is harder than it looks. You need consistent telemetry, enough context to interpret what you’re seeing, and dashboards that are actually useful when something goes wrong in production. This post covers how we integrated Peermetrics into an Amazon IVS Real-Time
For the third time, the video froze mid-sentence. The patient, trying to describe a worrying symptom, could only see a static image of her doctor. The promise of convenient, accessible healthcare was quickly turning into a frustrating, stressful experience for both parties. This scenario is an all-too-common
Last year, I attended the RTC.ON conference organized by Software Mansion for the first time. I shared my take on the conference in this WebRTC.ventures blog post: A WebRTC Developer’s Take on RTC.ON 2024. I also spoke at the 2024 conference, a recording of that talk is
If you’ve worked with WebRTC applications long enough, you’ve probably heard these complaints: “The video froze, but I could still hear them.” “The audio kept cutting in and out.” “The call just dropped for no reason.” You check your application performance monitoring (APM) dashboard and everything looks
