Which PWA Capabilities Are Supported on My Device?
Open whatpwacando.today in the browser on the device you want to test and use its built-in capability checklist. The site is itself a Progressive Web App, so it can report which PWA features your current browser and operating system actually support — installation, offline support, notifications, hardware access, and more — rather than telling you what is theoretically possible. Support varies by browser and OS, so the only reliable answer for your situation is the one your own device reports.
How the capability check works
The site's "PWA capabilities" section runs feature detection in your browser and shows a checklist of what is available right now. Because it is a live PWA, it also reflects whether the page is currently offline and whether installation is offered.
The demos below the checklist are live, not videos. Each one exercises a specific web capability so you can confirm support by using it, not just by reading a label.
Capabilities covered
| Capability | What the demo shows |
|---|---|
| Installation | A native install dialog via the beforeinstallprompt event |
| Offline support | Service Worker caching so the app works without a connection |
| Notifications | Notifications API, including when the app is not active |
| Declarative Web Push | Push notifications without a service worker |
| Shortcuts | Quick access to app pages from the app icon |
| View Transitions | App-like transitions between pages |
| Incoming Call Notifications | Call-style notifications |
| Geolocation | Sharing location with the web app |
| Media capture | Camera and microphone access |
| Media Capability Elements | Browser-controlled camera and microphone access |
| AirPlay | Streaming video from a PWA to an Apple TV on iOS or macOS |
The site advertises 40+ live demos in total, so the checklist is broader than this table — treat the table as the categories you are most likely to be deciding between.
Test your own device in four steps
- Open whatpwacando.today on the target device and browser.
- Scroll to the capability checklist and note which entries are marked as supported.
- Use the "Add to home screen" button once it becomes enabled — that confirms installation is offered on this device.
- Open the individual demos for the capabilities you care about and run each one. A capability that appears in the checklist still needs a real interaction (a permission prompt, a notification, a camera feed) to confirm it works end to end.
Expected result: you end up with a short list of capabilities your device supports today, plus the ones that fail or never prompt.
What to watch for
- Support is per browser and per OS, not per site. A capability that works in one browser on your phone may be missing in another, and desktop and mobile results can differ.
- Permission-gated features need a user gesture. Camera, microphone, geolocation, and notifications will not activate until you trigger them and accept the prompt. A demo that appears to do nothing may simply be waiting for that.
- Installation depends on install criteria being met. The "Add to home screen" button only becomes enabled when the browser considers the app installable, which is why the site tells you to wait for it.
- Offline behavior needs a prior visit. Service Worker caching happens after the app has loaded at least once, so test offline mode after an initial online visit.
If a demo fails
The site points to a free pwa-check tool for identifying and fixing implementation issues, and to a PWA Runtime Audit for integrating checks into a CI/CD pipeline. Use the first when a specific capability misbehaves on your device; use the second when you want consistent release confidence rather than one-off debugging.
The site also offers a weekly email update on PWAs and new features of the modern web, tested and explained in plain English, via a subscribe link.