One connection, every tab: background sync

One connection per browser keeps the organization's data in sync in the background, with a live shell that follows changes without polling.

The platform keeps the organization's data on your device and up to date while you work. This release rebuilt how that happens: one connection per browser instead of one per screen, and a shell that follows changes instead of asking for them.

One grouped connection

Every tab of a browser now shares one streaming connection that carries all subscriptions, possibly for several organizations. One tab holds it and relays frames to the tab that stores each collection. On the server, a change in one organization wakes only the streams that read it, bootstrap scans resume where they stopped, and in-flight reads are shared between streams.

Background by default

A feature declares the collections of an organization once, and they synchronize in the background for whoever may read them, in every tab where the organization is open. Screens load first; released collections keep synchronizing for ten minutes, so returning to a screen does not reload it. The sync status shows how much space is used on this device and warns once when it runs low.

A live organization shell

The organization menu follows a published setting that every member sees, the settings editor follows the live draft and publication rows, and the organization directory is built from each person's memberships. Nothing in the shell polls any more: no navigation refresh, no list of organizations on every session check.