Skip to content

Menu

Book a free consultation

Can a Web App Replace Your First iPhone App? PWA on iPhone in 2026

Push notifications, offline mode and a Home Screen icon all work in a PWA on iPhone now. Bluetooth, NFC and background tasks don't. Check before you build.

Mobile · 25 Oct 2026 · 5 min read

Can a Web App Replace Your First iPhone App? PWA on iPhone in 2026

ByWahib RizwanFull-Stack & Blockchain Engineer

For a lot of products, yes. A progressive web app (PWA), a website people save to their Home Screen, can now open full screen, work offline and send push notifications. What a PWA on iPhone still can't do is reach Bluetooth, NFC or USB hardware, run in the background or get into the App Store as a simple wrapper.

The trade-off matters because a native app means a separate codebase, Apple's review process and, for many products, an Android version too. And if you need one of the missing features, finding out after launch is expensive.

This capability check is based on Apple's WebKit announcements and browser support data as of late 2026. If you're deciding what to build first, it's the first conversation in any MVP app project we take on.

What changed recently

  • iOS 16.4 (March 2023): Web Push notifications and app icon badges for web apps added to the Home Screen.
  • iOS 17.4 (March 2024): Apple planned to remove Home Screen web apps in the EU under the Digital Markets Act, then reversed the decision after requests to keep them. They stayed, built on WebKit as before.
  • iOS 18.4 (2025): Declarative Web Push, a simpler way to send notifications that doesn't depend on a service worker running.
  • iOS 26 (2025): Every website added to the Home Screen opens as a web app by default, in its own window without Safari's interface, even if the site wasn't built for it. Users can switch this off when adding it.

Safari 27, released in September 2026, focused mainly on bug fixes, plus CSS, HTML and developer tool features, rather than new web app capabilities.

What a PWA on iPhone can do

Capability

Works?

Notes

Home Screen icon, full-screen window

Yes

Default for any site since iOS 26

Push notifications

Yes, once installed

Only for Home Screen web apps, and permission must follow a tap

App icon badge

Yes

Since iOS 16.4, for Home Screen web apps

Offline mode

Yes

Service workers and IndexedDB, within storage limits

Camera and microphone

Yes

While the app is open

Location

Yes, in the foreground

No background tracking

Passkeys and Face ID sign-in

Yes

Through WebAuthn

Online payments

Yes

Through the Payment Request API; test Apple Pay in Home Screen mode before you rely on it

Native share sheet

Yes

Web Share API

That's enough for booking apps, customer portals, internal tools, dashboards, ordering, loyalty programmes and most content products. Sign-in can be passwordless too: our guide to passkey authentication explains how it works and how to add it.

PWA limitations on iOS: what doesn't work

According to browser support data for iOS Safari 26 and 27, these are not available to web apps on an iPhone:

  • Bluetooth (Web Bluetooth). No fitness trackers, printers or other Bluetooth devices.
  • USB and serial devices (WebUSB, Web Serial).
  • NFC (Web NFC). No tapping tags or cards.
  • Background sync. The app can't quietly upload or refresh while closed.
  • Vibration (the Vibration API).
  • Background location, geofencing and anything else that runs while the app is closed.
  • Home Screen widgets, Siri shortcuts and Apple Watch apps.
  • Health data from Apple's HealthKit.

If your product depends on any of these, you need a native app, or a cross-platform one such as React Native that compiles to native.

Three catches that surprise people

1. There's no "Install" button

On Android, Chrome can show an install prompt. Safari can't. iPhone users must tap Share, then Add to Home Screen, and many don't know the step exists. Push notifications only work after it. Plan a short on-screen guide, shown at the right moment rather than on the first visit.

2. Storage isn't guaranteed forever

WebKit is generous: a single site can store up to 60% of the device's disk in a browser app, and Home Screen web apps get the same quota. But WebKit can delete a site's data when the device runs low on space, or when the user hasn't interacted with the site for some time.

Requesting persistent storage helps, and WebKit's documentation says it considers whether the site runs as a Home Screen web app when deciding. Still, treat on-device storage as a cache and keep the real data on your server. Our guide to offline-first billing software shows how to design around this when an app must keep working without a connection.

3. Notifications need the user to opt in, twice

First they add the app to the Home Screen, then they allow notifications after tapping something inside the app. If notifications are how you bring users back, expect to reach fewer iPhone users than a native app would.

Why not just wrap the website in an app?

It's tempting to put the web app inside a thin native shell and submit it to the App Store. Apple's App Review Guidelines push against this: guideline 4.2 says an app should "elevate it beyond a repackaged website", and 4.2.2 says apps shouldn't primarily be "web clippings". A wrapper with no native features is likely to be rejected.

If you need to be in the App Store, build something that earns its place there, with real native features.

A quick way to decide

Start with a web app if:

  • Your users come back through links, email, search or QR codes rather than App Store browsing.
  • The product is mostly forms, content, bookings, payments or dashboards.
  • You need iPhone, Android and desktop from one codebase, updated without app review.
  • You want to test demand before investing in native development. Our breakdown of what an MVP costs to build shows where the hours go in a first web version.

Go native (or cross-platform native) if:

  • You need Bluetooth, NFC, background location or health data.
  • Push notifications are your main way of bringing users back.
  • App Store discovery is part of your growth plan.
  • You need widgets, Siri, Apple Watch or deep offline use over days.

There's a middle path. React Native lets one team build real iOS and Android apps that share most of their code, and often some logic with a web app too. You can start with a web app and add a React Native app once you know which native features users actually need.

Frequently asked questions

Do PWA push notifications work on iPhone?

Yes, since iOS 16.4, but only for web apps added to the Home Screen. The user adds the app first, then allows notifications after tapping a button in it. They don't work for websites opened in Safari.

Can I put a progressive web app in the App Store?

Not as a simple wrapper. Apple's App Review Guidelines (4.2) say apps should go beyond a repackaged website, and wrappers without real native features are often rejected. For the App Store, build a native or cross-platform app.

What are the limitations of a PWA on iPhone?

It can't use Bluetooth, NFC, USB or serial devices, run tasks or track location in the background, add widgets or read HealthKit data. Safari also has no install prompt, so users must add the app to the Home Screen themselves.

The bottom line

On an iPhone in 2026, a web app can look and feel like an app, work offline, send notifications and take payments, but not reach hardware, run in the background or get into the App Store as a wrapper. Check your must-haves against that line before you build, not after.

Not sure which side of the line your product sits on? Book a free consultation and we'll go through your feature list with you and suggest what to build first.

Sources

Back to all insights

Keep reading.

Have a project in mind?

Tell us what you're building, what's slowing your team down or what you'd like to automate. We'll come back with honest next steps and a clear estimate.

Book a free consultationEmail us

No obligation and no sales script.

Popular searches

Change theme