WebRTC Weekly Issue #645
Google Meet trusts iOS Safari, MoQ keeps circling, and an AV1 reality check
This week Apple’s WebRTC support hit a quiet milestone: Google Meet now runs in Safari on iOS, no app needed. MoQ keeps showing up from every direction, and there’s an AV1 piece that falls apart the moment you remember who actually ships codecs at scale. Me? I spent it writing about how to read a webrtc-internals dump.
⭐ Tsahi’s Pick
Join Google Meet calls from Safari on iOS devices (Google)
Google Meet now runs in Safari on iPhone and iPad, no app required. For years Safari was the browser you warned users about when building on WebRTC, and Google kept Meet in its iOS app for a reason. If Google is now comfortable putting Meet into mobile Safari, Apple’s WebRTC support has quietly become good enough for one of the most demanding real-time apps out there. The question is whether the rest of the vendors follow and start trusting iOS Safari.
📰 This Week in WebRTC
How to debug a webrtc-internals dump with AI (rtcStats) - the AI-assisted counterpart to reading the dump by hand: upload one and get the what-went-wrong in under 30 seconds
POC time: a push-to-talk demo with MoQ (Meetecho) - Lorenzo keeps poking at MoQ, this time a working push-to-talk demo bridged to WebRTC and back
5 Reasons MoQ Streaming Is a Great Fit for Surveillance and Monitoring (Red5) - This reads future looking, based on the fact that implementations of MoQ don’t interoperate when not on the same draft yet
Berlin’s Almetra raises €16.3M to turn factory video into live data (The Next Web) - One wonders if live here means WebRTC or something else
AV1 in 2026: Why the ‘Next-Gen Codec’ Still Isn’t Dominant (Trembit) - I just love reading AI generated content and losing interest when the whole premise falls apart - 90% of WebRTC sessions use VP8 - that’s when Google Meet defaults to VP9 and uses AV1 - and are the biggest WebRTC player in town...
📣 Sponsor
Beyond WebRTC Projects: Build Your Complete Engineering Team (WebRTC.ventures)
You’ve reached a pivotal moment. Your WebRTC application is successful, user adoption is growing, and you need to expand development capacity significantly.
✍️ This Week on BlogGeek.me
How to Read a webrtc-internals Dump, Section by Section - my walkthrough of a webrtc-internals dump, section by section, so a bad call’s recorded data actually tells you what went wrong