Testing and Validation
You'll learn how to use browser DevTools and Lighthouse to verify your Web App Manifest is correctly configured and your PWA is installable.
Why Validation Matters
Creating a manifest file is only half the battle—you need to confirm browsers can actually read it and that your app meets installability criteria. Think of it like publishing a book: you don't just write the manuscript, you also need proofreaders to catch errors before readers see them.
DevTools Application Panel
Open Chrome DevTools and navigate to the Application tab. Under "Application" in the sidebar, you'll find the Manifest section. This displays:
- Parsed manifest properties (name, icons, display mode, etc.)
- Visual preview of icons and colors
- Installability warnings that explain why your PWA might not be installable
- A link to test the install experience
If there's a JSON syntax error or missing required field, DevTools will flag it immediately with clear error messages.
Lighthouse PWA Audits
Run Lighthouse (from DevTools > Lighthouse tab) and select the Progressive Web App category. Lighthouse checks:
- Valid manifest with correct properties
- HTTPS requirement
- Service worker registration
- Viewport meta tag
- Correct icon sizes (at least 192x192 and 512x512)
Each audit provides a pass/fail result with actionable guidance. A failing "installable" audit tells you exactly what's missing—maybe your manifest lacks a start_url, or icons are the wrong size.
Testing Installation
Use the "Add to home screen" prompt simulation in DevTools to test the actual install flow without deploying your app publicly first.
Key Takeaway: Browser DevTools validates manifest syntax and structure in real-time, while Lighthouse audits confirm your PWA meets full installability standards—use both to catch issues before users do.