← Back to Cross-platform mobile foundation team
See how it helps
Offline and interrupted mobile UX
Explains what remains available offline and preserves user intent through interruptions without implying unsaved work succeeded.
mobile-offline-interrupted-ux
Team members using this skill
When is it useful?
Use when connectivity loss or backgrounding interrupts a mobile task.
What does it help you do?
- Distinguishes cached content, pending changes and unavailable operations.
- Communicates sync status and offers useful recovery actions.
- Preserves drafts and context across interrupted sessions.
Try asking this
Design an offline inspection form showing saved-on-device answers and clearly pending server submission. Complete an inspection without a network, close the app and reopen it. Distinguish locally preserved answers from server-confirmed submission until synchronization finishes.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
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 all user-entered data and context, explain what happened in plain language, and offer a clear Retry or Save draft action.
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.
- Idempotent & safe recovery: Ensure that retrying after a lost connection or app restart does not leave the user confused about whether a sensitive action (payment, booking, submission) already succeeded.
Included files 1
SKILL.md