Replay’s Recording Roadmap

profile photo
Jason Laster
Image without caption
Tesla Model 3
We often talk about how we replay because that is where time-travel debugging happens, but it is just as exciting to think about how we record.
Videos have not changed that much in the past twenty years, but the availability of video recorders have. The iPhone put a video recorder in everyone’s hands. The Tesla Model 3 meant every accident was recorded. NBA instant replay changed the way the game was officiated.
Replay’s recording roadmap looks similar.

1. Democratized Recorder

If the Replay browser were based off of Chrome, it could be your default browser and the record button could be one click away. If you see an issue, you could click record, reproduce the bug, and share the replay with your team.

2. Always On Recorder

If you could click save whenever you see an issue, you would never have to worry about reproducing a bug. You could save the replay and share it with your team.
An always-on recorder also enables recording production environments such as Node backends and Electron frontends. At that point crash reports would include links to replay sessions!

3. Instant Replay

If replaying were instant, you could add a print statement in your editor and see the last 100 logs immediately in your editor’s console. The direct feedback would change local development.

Our Roadmap

In Q2, we will be focusing on recording end-to-end test in CI and ten minute recordings. This summer, we will develop the Chrome for Mac browser and begin exploring an always-on recording mode.
Related posts
post image
In this failure, we look into a bug where a React component calls Math.round and gets a different value when the test passes and fails!
post image
This week we’re excited to share Elements Panel V3, which brings one second element loads.
post image
Today we’re excited to share an entirely new version of React DevTools which Brian Vaughn wrote from scratch.
Powered by Notaku