service-manual 2 linked patterns checked
web.dev Offline UX design guidelines
Documents designing for slow, intermittent, and absent connectivity, educating users about what changes offline, visibly different local-save feedback, plain language, meaningful icons, and task continuity while offline.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Offline mobile retry | Choose offline mobile retry when a mobile action should be preserved and retried after connection loss, flaky network, app backgrounding, or policy-limited connectivity. | The UI never reports server success for a mobile action that is only saved locally or queued. | Supports task continuity, local-save feedback, and meaningful offline communication under intermittent connectivity. |
| Offline state | Choose offline state when connection loss changes what users can read, edit, save, submit, refresh, upload, export, or share. | The offline indicator appears only when connectivity affects the current task or a global app capability users can reasonably act on. | web.dev supports communicating what changes offline and visibly distinguishing local save from online save. |
Comparisons supported by this source
- Offline mobile retry vs offline state vs retry vs sync state vs pull to refresh vs fallback path
Supports task continuity, visible local-save status, and clear offline explanations for intermittent mobile connectivity.
- Offline state vs error state vs loading spinner vs progress bar
web.dev supports educating users about what changes offline and visibly distinguishing local save from online save.
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: web.dev. Last checked: .