Have been following Replay's progress for some time, and this is a huge improvement in state-of-the-art debugging that's easy to use. It's worth your time to get familiar with it ASAP.
Web dev tooling haven't seen a revolution like that since Firebug ๐ฅ Being able to replay bugs is huge, but I also dig the collaborative debugging concept. Congrats @jasonlaster11 and the team!
Replay.io will certainly make debugging the web better and more collaborative between your developers and the design, product, and QA team.
I have been following Replay's progress since its early days. When the team was working on the Firefox devtools debugger I was fortunate to be a part of the opensource community and learn some of the time travel debugging concepts. I am extremely happy to see Replay.io go live.
Congratulations to the team ๐ ๐ ๐.
We're using Replay at Stately and it's the future of debugging applications. Extremely useful, and should be a part of every front-end developer's toolkit.
Report
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.
@mark_probst Mark, you and your team have been invaluable during this beta period. So much activity, so many helpful data points, feature requests, bugs, insights, etc. We couldn't have gotten this far without you and your team, thank you so much for being an eager early adopter. The product is a lot more polished than when you first kicked the tires as a result!
Was lucky to see early stages of Replay when it was R&D at Mozilla, then its first incarnations as a real product, and Iโm HYPED for all the debugging and team communication goodness this will bring! Fingers crossed for a stable Chromium-based recorder next (current offerings seem to include recording Gecko and Node.js).
I had the pleasure to try out Replay in the Beta stage, and I must say it is the game-changer. I believe it won't be an exaggeration to say that it has the potential of replacing the traditional "bug reports".
Recording the video, making screenshots, carefully describing reproduction steps, dropping a ".har" file, all of that won't not necessary if you use Replay. It does it all for you, and more. Attaching a Replay to the bug report allows the person debugging to jump to any point in time of the bug occurrence and understand what has happened, which is the real essence of debugging.
No more "it works on my machine"! ๐
@kacper_klarzynski So good to hear from you Kacper, and thanks for being such a great beta tester! Everything you're saying is exactly what we were hoping to build, so thank you for helping us build it!
People use the word "game changer" waaaaay too often. Very rarely does anything change the game. But holy ๐คฌ, this just might!
I'm sharing it to all of my teams, even reaching out to teams at previous employers to make them aware of this magic. Great work!
Replies
Percy
SnappySnippet
Replay
Replay
WunderGraph
Replay
Ramp
WebContainer API
Replay
OpenWidget
Replay
Sukha
PromoRepublic
Replay
PromoRepublic
Replay