Most teams I've worked with talk about offline-first like it's table stakes. Then you dig in and find they're syncing every 30 seconds, have no conflict resolution strategy, and the "offline" experience is just a sad loading spinner.

Built a full offline app with RxDB last year. Worked great. Then we realized 85% of our users had decent connectivity and the sync logic was eating up 3 battery drains per day on older devices. Ripped it out. Now we cache reads, queue writes, and call it a day.

If your app actually needs true offline work (maps, notes, field work), go all in with proper CRDT or last-write-wins logic. Otherwise you're just adding redux middleware, custom persisting, and complexity for a feature nobody uses.

What's driving this for you. Is it real requirements or just architecture theater.