service-manual 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.
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. |
Evidence Role
This source is treated as service-manual evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: web.dev. Last checked: .