For a while now, our team has been trying to solve a common problem: getting all the context needed to debug a bug report without the endless back-and-forth. It’s hard to fix what you can't see, and console logs, network requests, and other dev data are usually missing from bug reports.
We’ve been working on a new tool called Recording Links. The idea is simple: you send a link to a user or teammate, and when they record their screen to show an issue, the link automatically captures a video of the problem along with all the dev context, like console logs and network requests.
Our goal is to make it so you can get a complete, debuggable bug report in one go. We think this can save a ton of time that's normally spent on follow-up calls and emails.
We’re a small team and would genuinely appreciate your thoughts on this. Is this a problem you face? How would you improve this? Any and all feedback—positive or critical—would be incredibly helpful as we continue to build.
PS - you can try it out from here: https://jam.dev/recording-links
If customer reports a bug (scenario/timestamp/user), company should be able to solve the issue.
Better yet, customer shouldn't really need to raise the bug, it should already be flagged by monitoring tools running on data above.
How would you compare this to session replay products? Is the main difference that you do it on-demand, vs. for all/sampled traffic?