2 May 2026
Offline-first honesty beats optimistic demos
Sync designs fail when demos assume perfect connectivity. Treat conflict and latency as first-class requirements.
Product demos love the happy path: open the app on a train, edit a record, watch it appear on another device. Production traffic includes tunnels, captive portals, and users who force-quit mid-write.
An honest offline design names conflict policy early. Last-write-wins may be fine for preferences and disastrous for regulated forms. Queue depth, retry budgets, and user-visible sync state belong in acceptance criteria, not a backlog labelled later.
Architecture consulting here is less about inventing a novel sync engine and more about forcing trade-offs into the open. Which fields are authoritative? Who resolves duplicates? What happens when two devices edit the same entity while offline for a weekend?
Teams that document those answers before coding save expensive rewrites after beta users invent failure modes nobody scripted.