The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup.

I highly recommend trying a modern setup from one of the many new local first solutions [2]

1. https://triplit.dev

2. https://www.localfirst.fm/landscape

Can someone explain this to me? I’m clearly missing something about its name.

Worked a treat

I wonder if this article is from the same people who made hood.ie? (i think it was sort of a backend/frontend library making it easy to build offline first apps, based on pouchdb). It was a really promising project but development stopped a few years ago, unfortunately.

Shameless plug: as there are many different libraries for creating offline first apps, i made a small list of them: https://github.com/yetke/offline-first

This approach means the tools have to be good at not just sync, but also querying, business logic, validation, authn, authz, trigger background jobs, etc. That's a lot!

I'm not trying to eliminate my backend, nor an all-in-one frontend DB. I've tried tools that do that, and I've come to think the approach has severe limits.

I wonder if there's not a way to offer a two-way stream of data change events, with conflict detection/resolution, which I can process with my own code.