Compatibility
Compatibility is a BCD-style data explorer that answers “Can I use X in a PWA?” across operating systems, browsers, versions — and, uniquely, country/region reach weighted by real-world browser share. It also covers the ecosystem-policy dimensions (ad networks, payments, store acceptance) that decide whether a capability is usable in production, not just whether it ships.
By featurePer-capability support matrices: OS × browser × version.
By OSFeature × operating-system pivot.
By browserFeature × browser-family pivot.
By country / regionEffective PWA reach weighted by real browser share — the differentiator.
Policy dimensionAd, payment, and store-acceptance policy as first-class compatibility data.
Features
Section titled “Features”Each feature has a canonical page with its OS × browser × version matrix, ecosystem policy rows, full provenance, and a machine-readable JSON export.
| Feature | Category | Summary | Targets |
|---|---|---|---|
| Background Sync | Capabilities | Defer actions until the user has stable connectivity via the service worker. | 7 |
| Badging API | Engagement | Set an app-icon badge (count or dot) on the installed PWA. | 7 |
| File System Access API | Capabilities | Read and write to the user's local file system with explicit permission. | 7 |
| Install Prompt (beforeinstallprompt) | Installation | Programmatic control over the PWA install prompt via the beforeinstallprompt event. | 7 |
| Manifest Protocol Handlers | Manifest | Register a PWA to handle custom or allow-listed URL protocols via manifest.protocol_handlers. | 7 |
| Payment Request API | Commerce | Browser-mediated checkout sheet collecting payment and contact details. | 7 |
| Service Workers | Capabilities | The programmable network proxy that powers offline, caching, and push for PWAs. | 7 |
| Web App Manifest: display | Manifest | The display member chooses the installed app's window mode (standalone, fullscreen, minimal-ui, browser). | 7 |
| Web App Manifest: scope | Manifest | The scope member fences the installed app's navigation boundary. | 7 |
| Web App Manifest: screenshots | Manifest | The screenshots member supplies richer install UI in browsers and store listings. | 7 |
| Web Push | Engagement | Server-sent push messages delivered via the Push API + service worker, even when the app is closed. | 7 |
11 features seeded and growing.
Compatibility data is rendered from machine-readable JSON and exposed as Dataset
JSON-LD, with a per-feature JSON export at /compatibility/<feature>.json so search and
LLMs can quote the source.