Checklist
PWA Readiness Checklist Before You Convert
August 4, 2026 · 5 min read
Ten minutes of checks before you build saves a rejected release later. Run this list in Chrome DevTools — the Lighthouse tab for scoring, the Application tab for manifest and service worker state.
The checklist
- Served over HTTPS with a valid, non-expired certificate.
- manifest.json linked in <head> with name, short_name, start_url and display: standalone.
- At least one 512×512 PNG icon, square, no rounded corners or transparency tricks.
- theme_color and background_color set — they drive the Android toolbar and splash screen.
- Service worker registered and controlling the whole scope, not just one path.
- An offline fallback page, or at minimum a cache-first strategy for the shell.
- First load under about five seconds on a 4G connection.
- No mixed content — every asset on an HTTPS page loaded over HTTPS.
- start_url resolves without a redirect chain.
Things that are not required but help
- Maskable icons, so Android can apply its adaptive shape cleanly.
- A short_name of 12 characters or fewer for the home screen label.
- Web push already wired up (OneSignal, Firebase Cloud Messaging) — it keeps working inside the app.
- A privacy policy URL, which the Play Console asks for during submission.
What happens if something is missing
A missing service worker will not block the build, but it weakens your case against Google Play's minimum functionality policy and removes offline loading. A missing 512×512 icon means Play rejects the listing. A manifest without display: standalone gives you a browser-looking app.
Ready when you are
Once the list is green, the conversion itself is the easy part — paste the URL, set the package name and icon, and download your signed APK and AAB.
Ready to ship your Android app?
Paste your PWA URL, get a signed APK and a Google Play ready AAB in minutes.
Build my app