Everyone claims to be magical.
Replay is actually magical!

It's a well known fact that engineers want high quality bug reports, with extensive details, reproduction steps, etc. Yet we have no tools for this other than praying that people follow a Markdown issue template. I think this tool has a very good chance of creating a new category around collaborative debugging. Well done Jason!

Replay.io is galaxy brain tooling. Real gamechanger.

I’m really excited to try this tool out, especially as I love any tool that can help to debunk the idea that debugging should or even can effectively happen alone.

I first saw Replay at ReactConf in 2019 and came away thinking "this is way cooler than anything I saw at the conference.

Programmers typically reach for debuggers when they run out of ideas on how to fix their code. Now coders reach for time-travel debugging to understand their programs and not just when they want fix a bug.

We've been using Replay at glideapps.com for a few months, and it's been a huge help in finding and fixing bugs. Our support team can record their reproduction of a bug and engineering can debug the replay at any later time to find the issue. Time-travel is also incredible.

I'm increasingly boggled by how much time we spend discussing how to write new code, when the majority of engineering time is spent analyzing existing behavior + reading existing code. Replay is an ideal power tool for learning how a system works.

Awesome to see time-travel debugging in such a usable, intuitive form!

Replay is the obvious next step for the future of collaboratively inspecting and debugging applications. This is going to be infinitely helpful for maintaining open-source projects, especially when reproducing bugs is difficult otherwise.