PWARegistry is a public source of normalized PWA data.
You do not need to scrape websites yourself.
You do not need to figure out which icon is best.
You do not need to manually separate mobile and desktop screenshots.
PWARegistry already does that work.
Your project simply retrieves the data it needs.
The simple model
A Progressive Web App publishes standardized PWA metadata on its own website.
PWARegistry:
- discovers it
- validates it
- normalizes it
- keeps it healthy
- exposes clean registry data
Other projects then use that data.
“Your project” can be a PWA store, a catalog, a launcher, a search engine, a software directory, a browser extension, or a research project. PWARegistry does not rank, feature, or review apps. That part is yours.
How it fits in your product
Do not fetch the whole registry every time a visitor loads a page. Copy the data you need, store a revision number, and update only when something changes.
Words used here
- Registry
- A structured public collection of PWA records.
- Revision
- A number that changes whenever the registry changes.
- Normalized data
- PWA data already cleaned up and interpreted consistently. You do not re-parse the Web App Manifest.
- Cache
- A local copy so you do not repeatedly download the same data.
- Static registry
- Cache-friendly JSON files under
/registry/v1/. This is the canonical source. - API
- A convenience way to look up and filter the same data under
/api/v1/.
Start here
- Quick Start — fetch one PWA in a few lines.
- Where the Data Lives — static files versus the API.
- Example: Build a PWA Store — a full, practical walkthrough.
Then pick the page that matches what you are building: one PWA, all PWAs, a category, search, icons, screenshots, or syncing.