What do you all do when users hit the Reload button, and it blows away your app-db? Is there an elegant approach to preserving state across reloads?

I was thinking of hooking into onbeforeunload and persisting to local storage, but just wondered if there was something else people were doing.

should your state persist across reloads?

most of my apps don’t want that

Here’s one use-case: my app embeds an iframe to a 3rd-party app, and sometimes the 3rd-party app gets into a bad state, and you want a reload without losing your work in the main/host app.

sure, just nothing that the question should be asked first 😅

noting*

:thumbsup:

usually I only need to persist a subset of the actual app state. so what I do is write to local storage on mutation

but the onbeforeunload sounds nice too, since it won’t slow down your app while it’s running

@manutter51 could you put a reload button on the iframe?

We’ve got one actually, but you know muscle memory — you think reload, and boom Cmd-R and you’re done.