Building offline-first applications introduces a massive technical hurdle: Data Synchronization. What happens when a user edits a document in Omnis while offline, but also edited it on their laptop? Resolving these conflicts without losing data requires resilient distributed systems.

The Sync Problem

Traditional apps use a straightforward REST API. You click "Save," and the server updates the database. If you are offline, the app simply throws an error. In an offline-first architecture, the "Save" action writes to a local SQLite database immediately. The complexity arises when the app finally reconnects to the internet.

Enter CRDTs

Conflict-Free Replicated Data Types (CRDTs) are the mathematical magic that makes offline collaboration possible. Instead of just saving the final state of a document, CRDTs track every individual keystroke and operation. When two devices sync, they merge their operation logs. Because the mathematical operations are commutative, both devices will arrive at the exact same final state without requiring a central server to dictate the "truth."

The Future of Sync

We are actively prototyping peer-to-peer (P2P) sync protocols. Imagine two users in a room sharing files or chat messages over local Wi-Fi Direct or Bluetooth, completely bypassing internet infrastructure. This is the ultimate expression of decentralized, resilient software.