Feature Requests

Visualizing Network traffic is a big part of debugging. what assets load what API calls are made websocket communication what does the app look like before/after each event

Firefox devtools shows GET/POST requests in the console. It would be nice to do something similar, albeit simpler. A good way to think about it would be logpoints, for API calls. This would give us a console message with the event arguments as well as an execution point that we could seek to where the requests were handled.

Autocomplete is a feature that is expected when writing expressions in the console.

When I'm paused in catch , i'd like to be able to jump back to where the error was thrown.

Occasionally a user would get a "session died unexpectedly error". The problem is, it doesn't give them any actionable information. Should they refresh, and it will work immediately after that? Or is there a bigger problem, in which case they should come back to view their recording in an hour or so? We should make it obvious which is which. In the case of the first one, if a refresh is all that's needed, we can save them a step by triggering the refresh for them.

The user should be able to collapse the toolbox and focus on the viewer and the timeline.

There should be a way for users to edit the title and description of their recording.

We've heard that users are often confused about what the timeline does when they're first introduced to Replay. Something that might help with onboarding users onto this concept is a filmstrip version of the timeline. The timeline would be composed of screenshots at various times during that recording, instead of the blank blue background that we currently have. Example below from iMovie.

It should be possible to limit who can view a recording.

We currently support async stacks for async/await we should also support more general stacks for promises, setTimeouts, fetches