platform-guideline 2 linked patterns checked

MDN PWA offline and background operation

Documents service-worker controlled pages, Cache API use, cache-first strategies, offline fallback pages, background synchronization, and intermittent-connectivity support for progressive web apps.

Read with a purpose

What this source can teach

Use this source to understand a platform convention and the setting it was designed for.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. 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 offline fallback, service-worker behavior, caching, and background operation for PWAs.
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. MDN supports service workers, Cache API strategies, offline fallback pages, and background operations for intermittent connectivity.

Comparisons supported by this source

Evidence Role

This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.

Publisher: MDN Web Docs. Last checked: .

Saved items