Offline and interrupted mobile UX

Offline & Interrupted Experiences

Design mobile flows that remain trustworthy, understandable, and recoverable under weak connectivity, network drops, and real-world interruptions.

Connectivity & Offline States

• Explicit offline capabilities: Clearly define what the user can view (cached content, stale-data indicators), create/save locally (drafts, queued actions), and retry when offline or on a flaky connection.
• Honest status communication: Never show a misleading "Saved" or "Synced" confirmation when an action is only queued locally or still pending network confirmation; distinguish Saved on device, Syncing…, and Failed to sync.
• Non-destructive error handling: When a request times out or fails, preserve user-entered data and context, explain what is known, and offer recovery appropriate to the operation's confirmed state.

Interruptions & Session Continuity

• Common mobile interruptions: Account for incoming calls, OS alerts, app switching (e.g. copying a verification code or checking another app), screen lock, background process termination, and auth token refresh.
• Draft & step persistence: Specify whether in-progress forms, multi-step flows, or unsaved edits are preserved in memory or persisted locally, and how the user resumes or discards them upon returning.
• Sensitive action recovery: A timeout does not prove a payment, booking, or submission failed. Design an outcome-checking state; hand operation identity, authoritative status lookup, and duplicate prevention to the backend owner. Offer resubmission only when that contract establishes it is safe; otherwise provide a pending/status-check or support path.

Recovery Handoff & Acceptance

• Deliver a state table covering local draft, queued, sending, confirmed, failed, and unknown outcome where applicable: retained data, visible status, allowed next action, and source of truth. Scope persisted drafts and queues to their account; define what happens on sign-out or account switching.
• Walk through connection loss before and after server acceptance, repeated taps, app termination/relaunch, and account switching. Verify preserved work returns to its owner, unknown outcomes never appear as success or definite failure, and replay cannot create duplicate sensitive actions. Separate observed backend behavior from a proposed UX contract.