Solving State That Survives a Refresh, and Match Records You Can Re-enter
A look back at sessionStorage in an education platform and the re-entry problem in a volleyball scoreboard. Data being saved and users continuing their work were different requirements.
Joohwan Yu · Founder, Full Stack Developer
Toris · Published
Contents
On the education platform, we had to keep the solving state after a refresh. On the volleyball scoreboard, there was a problem where, once you saved and left the browser, you couldn’t re-enter the existing match. They are different projects, but looking back, they lead to the same question: how far does the “save” that users talk about go?
A value existing in storage was not enough
On the education platform, we connected Zustand’s persist with sessionStorage to handle refreshes. This choice fit well with the requirement of continuing work in the current tab. But it doesn’t solve the requirement of closing the tab and continuing later on another device. If you don’t explain the scope of saving, developers and users end up thinking of different features under the same word.
For the volleyball scoreboard too, what users wanted was not a “saved” indicator but a way to reopen an existing match. The review notes at the time showed a direction that data saving and the re-entry path should be examined separately. If the key to restoring the data disappears from the screen, it is similar to the data having disappeared, from the user’s point of view.
If I wrote down the restore scenarios first
| User action | What to check |
|---|---|
| Refresh in the same tab | State serialization and initial restoration |
| Close the browser and revisit | Match list or a reopen link |
| Access from another device | A lookup path tied to the account and permissions |
| Open an old record | Compatibility with changed data formats |
This doesn’t mean every feature in this table must be implemented. What matters is to decide the supported scope first, and not to confuse the unsupported scope in the UI and design. If the structure uses invite links, you also have to think about recovery when the link is lost, and the permissions of whoever holds the link.
An experience that changed the definition of done
Now, I wouldn’t finish verification with just the response right after pressing the save button. I would check all the way through leaving the page, actually coming back, and opening the same record. I would also check, within that flow, whether the saved value and the value restored on screen match.
This experience made me look at the user journey before the storage technology. Data persisting is a condition of the system. Users being able to get back to work with that data is a condition of the product. Only by writing the two down separately did the missing path become visible.
Technical reference: MDN sessionStorage
Advertisement