I think it's fair to offer a look at what CouchDB says about conflict resolution and what's provided to help manage it. https://docs.couchdb.org/en/stable/repl

I think it's fair to offer a look at what CouchDB says about conflict resolution and what's provided to help manage it. https://docs.couchdb.org/en/stable/replication/conflicts.html https://docs.couchdb.org/en/stable/replication/conflicts.htm... After scanning that doc it looked to me like a developer could create a way to alert a user of conflicts and provide options to resolve them. On the client side it would seem like PouchDB might be used to create a friendly way to detect and help implement those decisions. I just started looking into conflict resolution this month, and more out of curiosity than need. PouchDB's "Live Sync" for feature CouchDB works amazinly well and that alone reduces the opportunities for conflicts substantially by insuring when you go offline you always have the latest data. As a rule of thumb I'd say that when using an app offline the user should avoid editing living documents. PouchDB makes it easy enough to create a new document with that data for others to review and merge into the living document when you come back online. But reality is conflicts will happen and we do need tools to deal with them, so it's great to see the Replicache team working on that.