For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/mobile/offline.md (or send Accept: text/markdown).
Offline access
A workspace-scoped read cache that keeps screens useful without a network.
What the cache stores
Under the app's document directory, JSON files in supastack-offline/ hold recent successful reads, named by a hash of the user, workspace, and key — raw identifiers never appear in paths. Entries expire after seven days, cap at 256 KB each, and corrupted or oversized files are deleted or refused. All cache I/O is best-effort and never blocks a screen.
Network first, cache as fallback
Cached reads always try the network and persist a fresh copy. The cache serves only on connectivity failures — an unreachable host or a status-0 client error. HTTP failures like 401 or 500 rethrow: denied resources never serve stale data, and a dead session is never extended by a cached reply.
When the cache is cleared
Sign-out clears everything, and signing in as a different account does too. Switching workspaces keeps the cache — scopes are isolated, so one workspace never reads another's rows.
What the user sees
Cached screens show a localized banner — You're offline, showing data saved some time ago — announced as an accessibility alert with relative times. The home, billing, notifications, content, commerce, and chat list screens read through the cache.
Verification and troubleshooting
Airplane-mode test each cached screen: reads survive, writes fail cleanly, and the banner reports the saved age. Sign out and confirm nothing of the previous account remains.