June Updates v1.7: Client Insights, a Dedicated API Host & Smoother Onboarding

Welcome to v1.7.0 of rtcStats! This release is about reading a session faster and getting started quicker: the Devices page becomes a real client view, summary widgets land on top of more pages, the public API moves to its own home, and a brand new onboarding path takes you from sign-up to your first insight.

Less hunting, more answers - let's dive in! 🧭

🚀 Major Improvements

> Summary Widgets & a Client-Focused Devices Page 🖥️

We reorganized the session viewer so the most useful signals are where you expect them. The Devices page now gathers the Microphone, Speaker, Webcam and Video widgets alongside a new System widget (browser, OS, screen resolution, memory and CPU cores), turning it into a true client view of the call.

On top of that, summary widgets now sit at the top of the Session and Content pages, giving you an at-a-glance read before you dive into the details. Everything renders consistently across the dashboard, /share and /embed, so shared and embedded sessions get the same overview.

Summary Widgets and a Client-Focused Devices Page

> A Dedicated api.rtcstats.com Host & an Observations Catalog 🔌 (Developer Plan)

The public REST + MCP API now lives on its own host: api.rtcstats.com, separate from the rtcstats.com website. It is a cleaner home for integrations and a clearer boundary between the product and its programmatic surface.

This release also makes observations first-class in the API:

• New GET /observations endpoint: a catalog of every major observation type, with the severity and tags each one can emit, so you know exactly which labels exist before you query.
• Filter GET /sessions by observation type: narrow your session list down to the ones carrying the issues you care about.
• Renaming cleanups and docs improvements: clearer field names and refreshed documentation across the API surface.

Read more in the API documentation.

A Dedicated api.rtcstats.com Host and an Observations Catalog

> A Smoother Onboarding: Quick Start, Docs, Support & What's New 🚀

Getting started should not require a manual. New accounts now get an in-dashboard Quick start checklist that walks you through importing, opening, tagging or commenting on, and sharing a session, with progress tracking and a dismiss or re-open control.

To back that up, we added a new Your First Session Knowledge Base article (with an inline "how to get a file to upload" guide on the Import page), a dedicated /support page that all support links now point to, and a What's new section on the homepage so you never miss the latest releases.

A Smoother Onboarding: Quick Start, Docs, Support and What's New

🛠️ Other Enhancements

> New Showcase: Netflix & FIFA ⚽

We added a new real-world showcase covering the Netflix FIFA streaming experience, another concrete example of how rtcStats is used to read and explain WebRTC sessions in the wild.

> Sharper AI Summaries Focused on Session, Content & Client 🤖 (Developer Plan)

We refocused the AI session analysis prompt on the three pillars that matter most: Session, Content and Client. The result is a tighter, more relevant summary that mirrors how the session viewer is now organized.

🐞 Bug Fixes

> Accurate Stats at Any Sampling Interval 📐

Per-second rates and per-frame averages were computed assuming a 1 second polling interval. When rtcstats-js sampled at a different interval, that produced inflated per-frame metrics (qpSum per frame, encode and decode time per frame) and zeroed candidate-pair packetsReceived/s and packetsSent/s. Rates and averages are now derived from the actual interval, so the numbers are correct whatever your sampling cadence.

📦 Ecosystem Updates

No changes to rtcstats-server or @rtcstats/rtcstats-js in this release - both stay on their current versions.

---

We're excited to see how you use the new client-focused Devices page and the dedicated api.rtcstats.com host to triage your WebRTC sessions! As always, the latest version of rtcstats-js is available - make sure you're up to date to get the best out of these new features.

Happy debugging! 💎