Replay - Your time travel debugger

Thanks Nick for hunting us! Hey everyone, it feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years! Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind. Here’s how Replay works today. Somebody on the team records a bug with the Replay Browser and shares the replay url with the team. From there, developers jump in and add print statements. The logs appear in the Console immediately so you don’t need to refresh and reproduce a thing. Over the past year we’ve talked to hundreds of users, recorded 2.5 million replays, and worked incredibly hard to ensure Replay would be fast, secure, and robust from the get go. Want to check it out? You can download Replay today. Can’t wait to hear what you think!

This is easily the most exciting development for webdev since browsers first started shipping DevTools When Jason first told me about Replay, I thought “no way that’s possible, and if it’s possible it will be a nightmare to actually use.” He sat down and gave me a demo and it shook me… This is some science fiction “ENHANCE!” shit

Such an awesome concept and incredible implementation so far. Really interested to see where y'all go from here.

Am so excited this is finally live! We've been using Replay for the last six months and it's saved us so much time debugging. Their team's also been SO generous with their time -- a masterclass in support. Well done!

One full week of efforts reduce to a matter of minutes. If this is not magic, I don't know what it is ! Go Findem. Highy recommend

Loom has been gamechanging for my bug reporting flow, so when I first understood this as "Loom for Developers" I was instantly hooked. The landing page itself will be instantly familiar to any fans of Bret Victor's time travel programming demonstrations - which is impressive enough, but making this work for any generic JavaScript, performant, sharable, and inspectable with familiar browser devtools is just killer. The topmost time consuming issue in triaging bug reports is reproducing them. Replay definitively solves the "can't repro this" problem.

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!

Super excited to see Replay officially launch. I've been blown away by their holistic approach to reimagining what debugging code should be like. Can't wait to use it myself.

Haven’t been blown away by a dev tool since… well, browser devtools. Incredible DX that makes debugging the gnarliest problems a breeze.

This is the natural extension of debugging, but the effort required to get is right is large. Really doing browser state right vs a hack that gets you halfway there (I'm fond of these, who doesn't love Redux time travel) really pays off in Replay. It feels so good to be able to trust the tool to produce a solid recording of behavior you don't yet understand. Replay is made possible by truly great tech that the team has pioneered. Replay makes bugs that would require deep subject matter expertise in order to find — developed instinct, really — solvable by the rest of us. You want to have this tool in your belt!