What if I am missing a feature?
How to request features, report gaps, and influence the rtcStats roadmap.
We build rtcStats based on real needs from real users. If something is missing, we want to hear about it.
How to request a feature
The easiest way to reach us is through any of these channels:
- Chat widget - the chat on the bottom right corner of rtcstats.com
- Email - support@rtcstats.com
- GitHub - open an issue on our rtcstats repository for anything related to the open-source components (rtcstats.js and rtcstats-server)
When requesting a feature, it helps us if you include:
- What you're trying to accomplish - the use case behind the request
- What you've tried so far - any workarounds you've considered
- How important it is - is this a nice-to-have or a blocker for adoption?
What to expect
We review every request and prioritize based on the impact it will have on our users. Here's how it typically works:
- We'll acknowledge your request and may ask follow-up questions
- If it aligns with our roadmap, we'll add it to our backlog and let you know our estimated timeline
- If it's a quick win, it might ship in the next release
- Paying customers' requests are given higher priority - that's one of the advantages of being on a paid plan. We also offer support plans for the open source projects for essentially the same reasons
Missing an Observation?
If you've analyzed a session and noticed something that rtcStats didn't flag as an Observation, definitely let us know. We're continuously adding new observations with every release, and user feedback is one of our primary sources for new ones.
Include the session URL (or a publicly shared link) when reporting a missing observation - it makes it much easier for us to investigate.
Was this page helpful?