Progressive web apps: benefits, limits and when to build one

What progressive web apps are, what they can do on iPhone and Android today, and when a PWA is a smarter investment than an app store app.

By the UK Technology Hub teamPublished 4 minute read

The short answer

A progressive web app is a website built to behave like an app. Users can add it to their home screen, it can work offline and, on supported devices, it can send push notifications, all without an app store. PWAs cost less than separate iOS and Android apps and update instantly. They're limited for some device features and app store visibility, especially on iPhone.

Not every app needs to be in the App Store. Progressive web apps, or PWAs, give users much of the app experience through the web, at a fraction of the cost of building and maintaining separate native apps.

What makes a web app "progressive"?

A PWA is a regular website or web app with a few extra capabilities:

  • Installable: users can add it to their home screen, where it opens in its own window like an app.
  • Works offline or on poor connections: a service worker caches key resources and data.
  • Push notifications: on supported platforms, the app can send notifications after the user grants permission.
  • Responsive: works on phones, tablets and desktops.
  • Secure: served over HTTPS.

What PWAs can do on iPhone and Android

Android and Chrome-based browsers have long offered strong PWA support, including install prompts, push notifications and many device features.

iPhone and iPad support has improved. Since iOS 16.4, web apps added to the home screen can receive push notifications after the user grants permission. Users install PWAs through Safari's share menu, and Apple doesn't show automatic install prompts, so you'll need to guide users. Some device features available to native apps remain unavailable or limited in PWAs on iOS.

Benefits for businesses

Lower cost. One codebase serves every device. No separate iOS and Android builds.

Instant updates. Changes go live immediately, with no app store review.

No app store fees on digital sales made through your own website checkout.

Discoverable on the web. PWA pages can be indexed by search engines, unlike content inside native apps.

Low friction. Users can start using it straight from a link, without a download.

Limitations to consider

  • App store presence: PWAs aren't automatically listed in the App Store. Some can be packaged for Google Play, and wrappers exist for the App Store, but Apple expects apps to offer more than a website.
  • Device features: advanced Bluetooth, background processing, some sensors and deep OS integrations may need a native app.
  • iPhone install friction: users must add the app manually.
  • Perception: some users expect a "real" app from the store.

When a PWA is the smart choice

  • Customer portals and account areas.
  • Ordering, booking and loyalty apps.
  • Field tools that need offline access to forms and data.
  • Internal tools for staff on mixed devices.
  • MVPs testing demand before investing in native apps.
  • Content and news experiences that benefit from search visibility.

When native is better

  • Apps relying heavily on device hardware or background tasks.
  • Games and graphics-intensive experiences.
  • Products where app store discovery is a key growth channel.
  • Apps needing the deepest integration with iOS features.

Our guide to iOS vs Android first helps if you do go native.

Building a good PWA

  1. Start with a fast, responsive web app. Performance is the foundation.
  2. Add a web app manifest with name, icons and theme colors.
  3. Add a service worker for caching and offline behavior. Decide carefully what works offline and how data syncs.
  4. Add push notifications with clear permission requests and genuinely useful messages.
  5. Guide installation with simple instructions, especially for iPhone users.
  6. Test across browsers and devices.

What a PWA costs

Because a PWA is a web app with extra capabilities, its cost is close to that of a well-built responsive web app, plus some extra work for offline behavior, notifications and testing across browsers. That's usually considerably less than building and maintaining separate iOS and Android apps. Our guide to app development costs explains the wider cost drivers.

A sensible path

Many businesses launch a PWA first, learn how customers use it, then add native apps for features that need them. A well-designed back end and API serve both. Our guide to creating an app covers this decision in the context of the full process.

How we help

Our web app development team builds fast, installable PWAs with offline support and notifications. As part of our wider app development service, we can package PWAs for app stores where appropriate, or build native mobile apps alongside when you need deeper device features.

Frequently asked questions

Do progressive web apps work on iPhone?

Yes. Users can add PWAs to the home screen, and since iOS 16.4 home-screen web apps can receive push notifications. Some features remain more limited than on Android.

Can a PWA be in the App Store?

Not automatically. PWAs can be packaged for Google Play, and wrappers exist for the App Store, but Apple expects apps to offer more than a website.

Is a PWA cheaper than a native app?

Usually, because one codebase serves all devices and there's no app store release process.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides for US businesses