Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing PWA readiness, adding an install prompt, or preparing a web app for submission to Microsoft Store or Google Play via PWA Builder.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-22 | ✓→✗ | ▼ Worse | 20% | 0% |
| case-20 | ✓→✓ | = Same ✓ | -27% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -1% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -17% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -23% | 0% |
Installable PWAs appear in the browser's address bar install prompt and in app stores, giving users a native-app experience without an app store listing. Studies consistently show that installed PWAs have higher engagement and retention than browser-only equivalents — users who install spend 3× more time in the app on average.
Check whether this site meets the PWA installability criteria: HTTPS, valid manifest, service worker, and appropriate icons.
Add or fix the web app manifest, ensure a service worker is registered, and provide correctly sized maskable icons.
Explain what makes a web app installable as a PWA and what the manifest display modes mean for the user experience.
Review the manifest.json and icon assets. Flag missing required fields, incorrect icon sizes, absent maskable icons, and any mismatch between start_url and the actual app root.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/pwa-installability
Other measured skills in the registry, with their headline benchmark lift.