Answer

How many users actually install PWAs?

Short answer

There is no single industry-wide install rate — it depends heavily on the product, audience and how the install prompt is presented. What is well documented is that several large companies (Twitter/X with Twitter Lite, Starbucks, Pinterest, Uber) have published PWA case studies reporting improved engagement, load times or conversion after launch, which is why PWAs remain a common choice for content and commerce sites.

By InstantPWA growth research·Reviewed July 25, 2026

Why there is no single number

Install rate depends on traffic source, how aggressively the app prompts for install, and whether the product benefits from repeat visits at all — a one-time-use tool will never see meaningful install numbers.

What public case studies cover

Companies that have published PWA case studies generally report on metrics like load time, data usage or session length rather than a universal "install rate" benchmark.

Where to find current data

web.dev’s case-study library aggregates company-reported PWA outcomes and is updated as new case studies are published.

Sources

web.dev — Case studies

What are some well-known examples of PWAs?

Well-documented production PWAs include Twitter Lite (X’s lightweight PWA for low-bandwidth markets), the Starbucks ordering PWA (built for reliable performance on slow connections), Pinterest’s mobile web PWA, and Uber’s m.uber.com PWA designed to work on low-end feature phones. Each company has published its own case study describing the goals and outcomes of its build.

Do PWAs improve conversion rate?

Yes, when users actually install. Published case studies (Alibaba, Twitter Lite, Pinterest, Uber, BookMyShow) show 30-100% conversion lift after PWA adoption — driven by faster loads, offline support and home-screen install. The effect is largely from install: once your icon sits on the home screen, return sessions jump.

PWA vs AMP: what is the difference?

AMP (Accelerated Mobile Pages) is a restricted HTML/JS framework designed to guarantee fast-loading static content, historically used to qualify for special placement in Google’s mobile search results. A PWA is a broader architectural pattern — HTTPS, manifest, service worker — that adds installability and offline support to any site, including AMP pages. They solve different problems and are not mutually exclusive, though AMP’s search-placement benefits have diminished since Google ended the AMP requirement for the Top Stories carousel in 2021.

What does theme_color do in a manifest?

The manifest’s theme_color field sets the colour of the browser’s toolbar (in a regular tab) and the title bar / task-switcher header for an installed standalone PWA, giving the app a branded look instead of the browser’s default grey or white. It can be overridden per-page with <meta name="theme-color" content="#hex">, which takes precedence over the manifest value while that page is open.

What is a maskable icon?

A maskable icon is a PWA icon designed with extra padding around the logo so that when Android applies its adaptive-icon mask — a circle, squircle or rounded square, depending on the device’s launcher theme — the important part of the logo is never clipped. You declare it by adding "purpose": "maskable" to an icon entry in the manifest, ideally alongside a separate "any" purpose icon.