Lessons learned building a service worker-first web app: Batching, OCC, and test
After working on offline-first web applications, I put together a reference implementation that demonstrates some architectural patterns I wish I'd had examples of earlier:
The interesting challenges: - How do you handle data mutations when users go offline mid-session? - What's a good strategy for batching API calls without losing user changes? - How do you test service worker behavior reliably? - How do you resolve conflicts when multiple users edit the same data offline?
This isn't a framework - it's more like a documented case study with working code. The README explains the architecture decisions and tradeoffs.
https://github.com/localnerve/jam-build
Looking forward to comments on the approaches I took or alternative patterns others have used.