Ask HN: Saving/restoring web-app state–useful or pointless?
1 points
32 minutes ago
| 0 comments
| HN
When working on large web apps, I often spend 30–90 minutes recreating the same flow just to reach the page I need to test.

I’m validating an idea:

A browser extension that can:

- save the current app state (URL, localStorage, sessionStorage, cookies, form inputs, scroll) - and restore it instantly so developers don’t have to rebuild long flows during testing.

Basically a “jump back to this exact screen and state” tool.

Would this actually help your workflow?

Or do most people rely on other methods (Cypress, mocks, backend resets, etc.)?

Looking for honest, critical feedback.

No one has commented on this post.