So then this can never work offline like a single page React PWA could then I guess? For me after seeing offline-first PWAs it's hard to want to go back to building stuff that's only available online, but I guess everyone's use-case is different.
But in more than ten years, offline mode have never been a requirement on any of the projects I worked on.
What I’m saying is that offline mode is just a feature like any other and it’s one with a huge cost in architecture complexity.
And, although it’s just my own opinion, I think if you want to be offline first, odds are that better stacks than the web exists for those needs.
The only use case I know is for map where you can download map so when you don't have 4G you will not be lost but that's the only use case I know.
They need to make sales order, survey, etc while offline and sync with our server whenever they get internet connection.
But yes we use pouch+couch to one way sync from our server to thousands device.
And from our sales force device to our server while we still save the data in pouch, we choose to use pwa's service worker to send directly to postgresql instead of pouchdb-couchdb sync.