How to use PWA Cache Scenario Planner
- Enter asset paths, strategy names and stored revision labels in editable rows or the advanced path | strategy | revision list.
- Enter a newer revision label to include update scenarios, or leave it blank to skip them. These are supplied labels, not inspected cache contents.
- Optionally include cold offline-navigation scenarios. The report can name a cache-only .html fallback candidate; it does not execute fallback delivery.
- Review scenario groups and unavailable/stale outcomes, then download the plan. Test actual service-worker behavior separately.
Example: PWA Cache Scenario Planner
Compare five supplied assets under six fixed scenarios; five offline asset/scenario combinations are unavailable in this model.
Options
- Strategy
- The model follows the printed strategy definitions. cache-first and network-first deliberately differ when an old copy exists.
- Fallback document
- The toggle adds a cold offline-navigation scenario. The first cache-only .html asset can be named as a fallback candidate, but fallback delivery is not simulated or installed.
- Assets and strategies
- One asset per line as "path | strategy | revision", for example "/app.css | cache-first | build-9". Paths are case-sensitive and limited to 160 characters; up to 30 assets. Strategies: cache-first, network-first, stale-while-revalidate, network-only, cache-only, revalidate.
- Revision available on the server
- A label for the newer deployment to model. Leave blank to skip the update scenarios.
- Model an offline fallback document
- Adds a cold offline-navigation scenario and identifies a supplied cache-only .html fallback candidate. It does not simulate serving a fallback response.
Supported inputs and limits
- Up to 30 assets with case-sensitive paths of 160 characters and revision labels up to 40.
- Six named strategy models use fixed online/offline and warm/cold assumptions; revalidate is a simplified declared strategy, not a full HTTP validation exchange.
- The fallback option adds a scenario and names a candidate only.
- No service-worker registration/lifecycle, cache write, asset fetch, runtime fallback or live offline guarantee.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A scenario plan needs a real implementation test
Revision labels describe your entered inventory, not verified browser cache contents. The model makes missing copies and stale revisions visible under its assumptions. Test a real service worker’s lifecycle, request matching and offline behavior separately before promising those outcomes to visitors.
Questions about PWA Cache Scenario Planner
Will it create a service worker?
It exports a plan without registering one.
Does an offline fallback always appear?
Only the declared fallback scenario is modeled; real behavior needs implementation and testing.
Are revision labels content hashes?
They are entered labels, not calculated asset hashes.