Last I was seriously looking at the PWA route, I understood that they were best suited for apps with always-online access because anything stored locally could be more or less jettisoned as soon as the device felt disk pressure. Is that still the case or did I dream that up?
However, the new File System Access apis (https://developer.mozilla.org/en-US/docs/Web/API/File_System...) that are landing in browsers will fix this. One of the things it does is enable very efficient block level read/write access to a privet sandboxed filesystem for the websites origin, perfect for persistent sqlite. There is more here: https://web.dev/file-system-access/#accessing-files-optimize...
For persistence across browsers/devices I provide the possibility to sync data over Dropbox and Google drive.
I lost my Wordle stats thanks to that feature :(
In the morning, it syncs pouchdb with couchdb server, cache all the pages then goes to offline first mode.
Anytime they get internet signal, the serviceworker would send the data to postgresql.
Pouchdb takes care of sync and all the multi browser storage problem.
It has a very aggressive stale bot closing issues (this search shows 700 closed stale issues https://github.com/pouchdb/pouchdb/issues?q=is%3Aissue+stale...), some which I really don't think it should have. It gives the impression of a very active but stable platform that I don't necessarily think is accurate.
For example I found a version hash collision bug while working on a side project, the issue was closed as stale (https://github.com/pouchdb/pouchdb/issues/8257)
But the core features (store JSONs locally, sync them up with CouchDB) have been stable and reliable for many, many years and just work.