crdt-example-app VS redux-offline

* https://www.youtube.com/watch?v=DEcwa68f-jY

And his demo implementation (and annotated fork):

* https://github.com/jlongster/crdt-example-app

Better protocols lead to improved UX (eliminating user-facing errors and offering faster updates) and DX (shifting errors left) and they're so relevant to the "why are you avoiding REST" debate that I split them out to their own category. Technically of course, whatever protocol you use may be a layer atop of REST - if you have a separate layer (like CRDTs) that handles syncing/conflict resolution, then that is the protocol you are really using.

Further Reading: Redux Offline Documentation

I haven't ever tried to build an offline-capable app myself, but from looking at things like https://redux-offline.github.io/redux-offline/ it seems based on capturing actions that describe what requests need to happen, akin to how sagas usually work, as opposed to using thunks that are just "a function that executes and then dispatches actions".

Offline. Both Firebase Firestore and Amplify AppSync also support offline persistence. Since they know your database schema, it's easy to offer a local replica and conflict resolution. There are vendor agnostic alternatives like RxDB or Redux Offline that take more glue work. Being Offline-first requires you to have a local replica of your data, which means that doing CRUD against your local replica can be much simpler (see below).

https://github.com/redux-offline/redux-offline Worth a look as well