October Updates (2): A new design and connection insights

We are excited to announce our latest release 🥳

This update is packed with significant changes, headlined by a major redesign of our Internals page to help you find and debug issues faster. We've also added a powerful new set of observations aimed directly at the connection setup phase - one of the most critical parts of any WebRTC session.

Let's dive in 🤿

🚀 Major Improvements

> A Fresh Look: The New Internals Panes 🥸

The biggest change you'll notice is the completely redesigned Internals page. As we've added more monitoring capabilities, the page was becoming dense and required a lot of scrolling to find specific data. And one thing we hated was having an infinite scroll of death - our sole purpose is to make your life easier - not harder.

To address this, we've split the page into five focused panes:

• Overview: Your starting point for the high-level summary including the observations
• Connections: A dedicated view for everything related to peer-to-peer connection status, including ICE Connectivity and DTLS
• Streams: All your media stream (audio/video) metrics in one place as well as the Data Channels.
• Devices: Information on the capture and output devices being used
• Logs: A focused pane for raw event logs

This new tabbed design allows each section to provide more detailed information without overwhelming the user. You can now jump directly to the area you need to investigate.

It also helps on page loading speeds and direct linking.

New Internals panes design

> New Connection Setup Observations 🔍

Hand-in-hand with the new "Connections" pane, we're introducing six new observations around the connection setup phase and the completeness of the capture itself. Failures and delays before media ever flows are notoriously difficult to pinpoint, and that is exactly where these land: open a session and you can tell at a glance whether something went wrong on the way in.

While we're at it: open the webrtc-internals page before the call, not during it. Start it too late and part of the session is simply not in the file. Better know about it early on…

Connection setup observations

✨ Other Improvements

As usually, we've had some other improvements done here and there around our service:

> Improved Invite Flow

We've added a small but significant quality-of-life improvement. Now, when you sign in, any existing invitations tied to your email will be displayed directly on your dashboard. You can accept them with a single click, removing the need to dig through old emails.

Improved invite flow

> NextJS Migration

Finally, from a technical side, we migrated our stack to the latest NextJS 16.0. This keeps our platform modern, performant, and secure, allowing us to build and iterate faster. This also provides faster rendered pages.

🔧 Important Requirement

> Chromium M143 Support

We've updated our parsers to take into account the new event names (e.g., on...) introduced in WebRTC Internals starting with Chrome M143. This ensures we stay in sync with the latest browser changes.

---

We're confident that these new features and improvements will help you diagnose and resolve WebRTC issues more effectively. We're always eager to hear your feedback, so please don't hesitate to reach out and let us know what you think of the new release.