Where to Get Help With PWA Implementation Issues
If you hit problems implementing PWA features, What PWA Can Do Today points to two concrete resources: the free pwa-check tool for identifying and fixing issues, and the PWA Runtime Audit for consistent release confidence when integrated into your CI/CD pipeline. The site also runs a weekly email list covering PWA updates and new web features, tested and explained in plain English. Which one you need depends on whether you're debugging a one-off problem or trying to catch regressions across releases.
Start With pwa-check for Debugging
The site's own guidance is direct: "If you run into issues when implementing a PWA you can run the free pwa-check tool to help you identify and fix them."
Use it when:
- A feature works in your demo test but not in your actual app
- Installation prompts don't appear
- Offline behavior is inconsistent
- You're not sure which capability is failing
The tool is described as free, so it's the lowest-friction starting point before you invest time in manual debugging.
Use the PWA Runtime Audit for Release Confidence
The site distinguishes between fixing a problem and preventing one. For "consistent release confidence," it recommends integrating the PWA Runtime Audit into your CI/CD pipeline.
The difference in practice:
| Situation | Better fit |
|---|---|
| Something is broken now | pwa-check |
| You want to catch PWA regressions before shipping | PWA Runtime Audit in CI/CD |
| You want to know what's supported on a given device | The site's capability checklist and live demos |
A runtime audit runs as part of your pipeline, so failures surface at build time rather than after deploy.
Check Device Support Before Assuming a Bug
Not every failure is an implementation error. The site is itself a PWA and includes a capability checklist plus 40+ live demos, so you can test what your device actually supports. If a demo doesn't work on your device, the problem may be the platform rather than your code — worth confirming before you spend time debugging.
Stay Current on PWA Changes
The site offers a weekly email list with "an update on PWAs and new features of the modern web, tested and explained in plain English." This is useful when a feature you rely on changes behavior or when a new capability becomes broadly available. Subscribe from the site's "Stay up to date" section.
Quick Decision Path
- Something is broken → run pwa-check first.
- You want to prevent breakage across releases → add the PWA Runtime Audit to CI/CD.
- You're unsure if it's your code or the device → test against the site's live demos and capability checklist.
- You want to keep up with changes → join the weekly email list.