Every app is collaborative. Automatically.
Real-time and offline are the two features every backend tells you to bolt on later — and later means a sync vendor and a rewrite. Here they are properties of the database: writes land locally first, every client is kept current, and the transaction manager reconciles on reconnect.
Your app works on a train.
Watch a phone add items, lose the network, keep working, and sync the queue when it comes back.
| Item | Updated (UTC) |
|---|
Four things the database does so that you don't.
Local-first writes
The SDK caches data on the device and pumps it to and from the database in real time.
Data-change listeners
Listeners fire when anyone else adds, moves, renames or removes an object.
Selective exchange
Share an item with identities or groups, or publish a view of it and let others subscribe.
Coordination on reconnect
Cached changes sync when the network returns; XML objects merge as deltas across identities.
What ships today, and what is alpha.
Real-time propagation and offline caching
Local-first cache, connected clients kept current, listeners, sharing, and sync on reconnect.
Simultaneous editing of one document
The Real-Time SDK that merges deltas from several identities in one XML document is in alpha — not for commercial deployments yet.