Comment by apatheticonion

Haha that was an entertaining read, thanks for sharing. This is also my third attempt.

The first was much like this one with browser storage. There was a bug in Chrome that wiped out the persisted storage of all websites which nuked all of my records

https://www.bbc.com/news/technology-50809216

I tried rewriting it in React because it was the new hotness but spent so much time worried about component rendering cycles, hooks, state that just ended up distracting me away from time on the UI and UX. It was fast (like it matters), but ugly.

As for data sync, I've just added SQLite on the client and going through the painful process of normalizing the records.

My idea is, users will be able to supply a Turso API key and the app can sync against that, keeping a local copy of the data - eventually consistent.

I'll probably do something dumb like keep a timestamp of the last change and push/pull data periodically.

It only works because it's 1 person using the app and no one trains with two phones