Persistance for local/offline experience

[ignatz]

We briefly touch on it during our TrailBase discussion and I would like to better understand:

• what the current recommendation is?
• and what the future direction may be?

Concretely, imagine the todo example app, but:

1. starting w/o a server connection presenting the last known state.
2. mutations performed w/o a server connection will eventually be reconciled (even if the app is closed before a connection is re-established)

Anyway, I wanted to build a proof-of-concept and was curious if this is already possible with the existing primitives at least in theory? - I don't mind getting my hands dirty and implementing the logic around TS/db, if at all possible.

Thanks 🙏

PS: I was browsing the git history and came across "persisting transactions to indexdb" and was curious if that was connected?

[KyleAMathews]

We've been discussing this in #82 — so more details there. Would love (more) of your help!

I was browsing the git history and came across "persisting transactions to indexdb" and was curious if that was connected?

Kinda — an early prototype did persist transactions to indexeddb until they were persisted but I realized this should be an opt-in thing as there's a lot of nasty edge cases to consider — see my useOfflineMutation suggestion #82 (comment)