Progressive web apps: when a PWA beats an app store app
A PWA is a website that installs to the home screen, works offline and can send push. When it beats a store app, and where iPhones still limit it in 2026.
By Sohail Hussain16 November 20266 min read
A progressive web app beats an app store app when your users come back often enough to want a home-screen icon but not often enough to install a store app, when most of them are on Android, and when the features you need are offline access, installs and notifications rather than background location or Bluetooth on iPhones. A PWA is a website with a manifest and a service worker. It is found through search, installs from the browser, updates instantly, pays no store commission and costs roughly a third to a half of a cross-platform app to build. Its weak spot, as of October 2026, is the iPhone: installs are manual and some device features are missing.
We build both PWAs and store apps as part of our mobile app development work, and we recommend the PWA more often than clients expect.
What is a PWA, in practice?
Three things turn a website into a PWA:
- A web app manifest. A small file with the app's name, icons, colours and how it opens. It lets the browser install the site to the home screen and open it without the address bar.
- A service worker. A script that sits between the site and the network. It can cache pages and data for offline use and receive push messages.
- HTTPS. Required for both.
Everything else, the screens and the backend, is the website you already have or are building. In Next.js, the framework we build most sites with, the manifest is a single file in the app folder, documented in the Next.js PWA guide:
// app/manifest.ts
import type { MetadataRoute } from "next";
export default function manifest(): MetadataRoute.Manifest {
return {
name: "Acme Field Orders",
short_name: "Orders",
start_url: "/",
display: "standalone",
background_color: "#ffffff",
theme_color: "#0f172a",
icons: [
{ src: "/icon-192x192.png", sizes: "192x192", type: "image/png" },
{ src: "/icon-512x512.png", sizes: "512x512", type: "image/png" },
],
};
}
The icons need several sizes; our app icon generator produces them from one square image. The service worker is where the real work is: deciding what to cache, how to update it, and what the app shows offline.
What can a PWA do on Android and iPhone?
The two platforms differ more than anything else in this decision. As of October 2026:
| Feature | Android (Chrome) | iPhone (Safari and other iOS browsers) |
|---|---|---|
| Install to home screen | Yes, with an install prompt you can trigger | Yes, manually from the share menu |
| Opens full screen, no address bar | Yes | Yes |
| Offline use through a service worker | Yes | Yes |
| Push notifications | Yes | Yes, only once added to the home screen (iOS 16.4 and later) |
| Icon badge with a count | No; Android shows a notification dot | Yes, for home-screen apps |
| Background sync when back online | Yes | No; sync when the app is opened |
| Camera and photo upload | Yes | Yes |
| Location while open | Yes | Yes |
| Background location | No | No |
| Bluetooth and NFC | Yes (Web Bluetooth, Web NFC) | No |
| Apple Pay or Google Pay | Yes | Yes |
The iPhone row that matters most is push. On Android, a visitor can allow notifications from the website. On an iPhone, they must first add the site to their home screen and then allow notifications from inside it, as described in WebKit's announcement of web push for web apps on iOS. Most visitors never do the first step unless you show them how. If reliable notifications to iPhone users are the core of your product, a PWA is the wrong tool.
Storage is the other caveat. Browsers can clear a site's stored data under storage pressure, and Safari clears data for sites that have not been used for a while. Installed home-screen apps are treated more generously, but a PWA should always treat the server as the source of truth and the device as a cache.
When does a PWA beat a store app?
Occasional but repeat use. A customer portal, a booking tool, a supplier catalogue. People come back monthly, want to stay signed in and appreciate an icon, but will not install a store app for it.
Staff tools on Android devices. Field staff, warehouse scanners, delivery drivers on company-issued Android phones. Android gives a PWA install prompts, push, offline use and even Bluetooth, without a store listing or review.
You need search traffic. A PWA is a website. Every product, article and listing can rank in Google. An app's screens cannot.
You want instant updates. No review queue, no waiting for users to update. Every visitor gets the new version on their next load.
You sell digital goods or subscriptions. Payments in a PWA go through your own gateway, with no store commission. In-app purchases vs web payments explains why that matters in store apps.
The budget is limited. If you already need the website, making it installable and offline-capable costs a fraction of a separate app and adds nothing to the yearly store maintenance.
When does a store app still win?
- iPhone-heavy audiences who need push. In the UAE and Saudi Arabia in particular, a large share of paying customers are on iPhone.
- Background location or hardware on iOS. Delivery tracking with the screen off, Bluetooth printers, NFC tags.
- Discovery and trust in the stores. Some audiences look for an app in the store first, and a store listing reassures them.
- Heavy offline data on iPhones. Large offline datasets are more dependable in a native app's own database than in browser storage.
- Home-screen presence without asking. Store apps get their icon on install. PWAs on iPhone depend on the user finding "Add to Home Screen".
If two or more of those apply, compare the options in do you need an app, or is a mobile website enough before committing to a store app.
Can you put a PWA in the app stores?
On Google Play, yes. A PWA can be wrapped as a Trusted Web Activity with tools such as Bubblewrap or PWABuilder and published as a normal listing. The site must prove it owns the app through a Digital Asset Links file, and the listing follows the usual Play policies, including the data safety form and target API level.
On the App Store, not in a useful way. Apple's App Store Review Guidelines (4.2, Minimum Functionality) reject apps that are a repackaged website without app-like features. If an App Store presence matters, it needs a real app, which is the route the mobile app development guide covers.
What does a PWA cost compared with an app?
As a planning ratio, a PWA costs roughly 0.3 to 0.6 times a cross-platform app with the same screens, because there is one codebase, no store submissions and no native modules. The backend and admin cost the same either way. The saving grows after launch: no developer accounts, no yearly SDK deadlines and no store review for each release.
If you already have a modern website, adding a manifest, icons, an offline page and push notifications is a short project measured in days or a couple of weeks, depending on how much must work offline. Full offline editing with sync is a different scale of work; offline-first apps explains why.
Was this guide useful?