Baseline should become the support budget for every PWA roadmap

Why this matters

A PWA listing can be technically correct and still disappoint users if its core features only work in one browser family. Installable web apps live in a strange middle ground: they are distributed like websites, but users judge them like apps. That makes browser support a product promise, not a developer footnote.

Baseline, as described by web.dev, is designed to bring clarity to browser support for web platform features. It helps teams understand which features are ready to use today and whether a project can trust a certain level of compatibility. For OpenPWA, that language is extremely useful: every listed app needs a support budget.

What changed

Baseline is no longer just an educational label. The web.dev Baseline page highlights tooling adoption, including integration patterns for Browserslist, CSS tooling, DevTools, and Web Platform Dashboard data. This means compatibility can move from “manual research at the end” to “release policy at the beginning”.

For PWA builders, that shift matters because features such as storage, push, install prompts, file handling, and advanced CSS all affect the installed experience. If a capability is not broadly available, the app can still use it, but the listing should explain the fallback.

What builders should check

Use Baseline as a release rubric:

• Identify the app's must-have features, not every feature in the codebase.
• Mark each feature as Baseline, newly available, limited, experimental, or browser-specific.
• Decide which features are allowed to be progressive enhancements and which are required for the app's main value.
• Reflect platform caveats in the OpenPWA listing instead of hiding them in documentation.
• Re-check support when launching a major redesign, not only when adding a new API.

OpenPWA angle

OpenPWA should treat compatibility as marketplace metadata. A useful PWA directory should not merely say “Chrome supported” or “mobile supported”. It should help users understand whether the app is reliable in the browsers they already use.

Baseline gives the newsroom a neutral language for this. Instead of making vague claims, OpenPWA can write: this feature is broadly ready, this one is still a progressive enhancement, and this browser-specific behavior should not be the whole product promise.

Sources:

• web.dev: Baseline