A local-first workspace that remains useful offline

Local-first is about the working copy

When an encrypted local copy is available, Standard Space can open existing Entries without waiting for a cloud round-trip. Edits made without the required network services are recorded locally and can synchronize after connectivity and authorization return.

That is different from a browser-only workspace that treats the remote service as the sole live copy. It is also different from claiming that every item is always available offline: a large attachment that was never downloaded to the current device cannot be opened from local storage merely because its Entry exists.

Three states, reported separately

SovaSpace distinguishes conditions that are often collapsed into a single green or red indicator:

• Local availability asks whether the encrypted data needed for the action is present on this device.
• Network reachability asks whether the device can reach the services needed for the current operation.
• Drive authorization and quota ask whether the connected account can read or write the required encrypted objects.
• Pending durable work shows whether uploads, downloads, deletes or synchronization tasks still need attention.

An operation is not presented as complete merely because the interface accepted a tap. Pending work remains visible and retryable when a required service is unavailable.

What can continue offline

Locally available Standard Space Entries can be read and edited offline. Local search and editing depend on what has already been stored on that device. New changes are preserved locally for later synchronization.

Availability differs by feature. Secret Spaces apply stricter foreground and unlock boundaries. Cloud-only attachments require a successful fetch before they can be used locally. Account changes, new trusted-device actions and other server-coordinated operations require the appropriate service.

Conflict and recovery expectations

Offline capability reduces dependence on a momentary connection; it does not remove the possibility of conflicting edits, device loss or cloud deletion. Users should let pending work finish before intentionally switching devices, and they should keep an independent recovery path for important data.

The app's one-active-session model makes a deliberate device handoff visible. Activating another supported device ends the previous active session without deleting that device's local encrypted data.

A practical offline checklist

1. Open important Entries and attachments on the device before a planned offline period.
2. Confirm that pending durable work has completed before leaving a reliable connection.
3. Check local storage capacity independently of Google Drive quota.
4. Return online before making a device handoff when possible.
5. Maintain a tested independent recovery copy for irreplaceable material.

Offline-capable means locally available work can continue; it is not a promise that every remote object, account action or file format works without a network.