What PWAs can and cannot do on iPhone in 2026

An iPhone PWA capability survey from consultancy WAVX solutions lists what works and what does not. It gives the versions and conditions for each capability. Published on DEV Community on 2026-10-04, its sources include WebKit release notes and Apple documentation, along with MDN data. The authors say they read these on 2026-10-02 (WAVX solutions).

Supported capabilities and their conditions

The survey divides supported capabilities into four groups: installing and launching; offline storage; notifications; device access. Each item has a stated iOS version or condition (WAVX solutions).

Installing and launching

Adding a site to the Home Screen from Safari is described as working in the ordinary way, with no manifest trick required. The survey adds one behavioural change it dates to iOS 26: every site added to the Home Screen opens as a web app by default. It also reports that third-party browsers on iPhone, including Chrome and Edge as well as Firefox, have been able to install a site through the Share menu since iOS 16.4, and that manifest icons are used from iOS 15.4 when a page carries no apple-touch-icon. WebKit says iOS has supported multiple installs of the same web app since the beginning. In iOS 16.4, the user-selected Home Screen name is combined with the manifest id to identify each installation; using the same name on multiple devices also lets Focus settings synchronize (WAVX solutions; WebKit).

The survey dates a standalone app window to iOS 11.3 and says MDN’s data lists the fullscreen and minimal-ui display modes as unsupported in Safari. It also qualifies manifest icon support: from iOS 15.4, the icon is used when the page has no apple-touch-icon and the manifest icon’s purpose is any or is unset. Manifest shortcuts remain in the does-not-work column for iPhone (WAVX solutions).

Offline and storage

Service workers and the Cache API are dated to iOS 11.3. Navigation preload is listed from iOS 15.4, and the survey records the Service Worker static routing API arriving in iOS 27. MDN describes that API as a way to specify static routes that “define rules for fetching specified resources that will be used even before service worker startup”, with a source of network, cache, fetch-event, or race-network-and-fetch-handler, and it classifies the feature as having limited availability across browsers (WAVX solutions; MDN).

The storage figure the survey quotes, around 60% of disk per origin since iOS 17, matches WebKit’s own storage policy post, which states that starting in Safari 17.0 and in WebKit apps for iOS 17, iPadOS 17, and macOS Sonoma, “the origin quota is up to 60% of the total disk space” for a browser app. That post also states that a web app running standalone from the Home Screen “has the same origin quota and overall quota as when it is opened in a browser app”. Standalone mode is not a separate storage tier (WebKit).

For script-writable storage, the survey reports a seven-day rule applying after seven days of Safari use without interaction on the site, with Home Screen web apps given their own counter based on actual use of the app. The survey also says each installation on Apple devices has its own storage, and advises planning for a visitor who signed in on the site in Safari to sign in again inside the installed app (WAVX solutions).

The same table dates persistent-storage requests to iOS 15.2 and says Safari decides them with heuristics that include whether the site opens as a Home Screen web app. It places navigation preload at iOS 15.4 and static routing at iOS 27. The unsupported column includes Background Sync and Periodic Background Sync along with Background Fetch (WAVX solutions).

Notifications

Web Push is in the works column with conditions dated to iOS 16.4: Home Screen web apps only, permission requested only in response to a tap, and every push obliged to show a notification. WebKit’s own announcement post backs the first two directly. It says “a web app that has been added to the Home Screen can request permission to receive push notifications”, qualified by “as long as that request is in response to direct user interaction such as tapping on a ‘subscribe’ button”, and it confirms Badging API support for Home Screen web apps on iOS and iPadOS 16.4 along with Focus integration, which lets users configure when or where notifications arrive. The same post also says: “You do not need to be a member of the Apple Developer Program to use it.” The survey adds Declarative Web Push from iOS 18.4 as a path to displaying a notification without JavaScript, and notes that a server sending push must be able to reach https://*.push.apple.com if outbound traffic is restricted (WebKit; WAVX solutions).

The survey separately lists the Badging API and Focus modes from iOS 16.4. It describes Declarative Web Push from iOS 18.4 as a Home Screen web-app feature that can display the notification without a service worker. Its unsupported notification options include action buttons and images as well as vibration patterns (WAVX solutions).

Device access

Camera and microphone access is dated to iOS 11, geolocation and Web Share to iOS 12.2, and Screen Wake Lock to iOS 16.4 in Safari with Home Screen web apps following in iOS 18.4 (WAVX solutions).

The device table also lists the Vibration API as unsupported and the Contact Picker as disabled by default behind a preference flag from iOS 14.5. Its entry for getInstalledRelatedApps says an iPhone PWA cannot use that API to detect an installed native app (WAVX solutions).

What the survey places in the does-not column

There is no beforeinstallprompt event on iPhone, and the survey states flatly that the event exists only in Chromium browsers. MDN agrees, and describes BeforeInstallPromptEvent as non-standard (WAVX solutions; MDN).

Background Sync and Periodic Background Sync are unsupported according to the survey, as is Background Fetch. It says queued work completes only while the app is open (WAVX solutions).

The survey lists Web Bluetooth and Web NFC as unsupported, along with WebUSB. Within notifications, it reports that action buttons and images are unavailable, as are vibration patterns. It also lists getInstalledRelatedApps as unavailable (WAVX solutions).

Significance for iPhone installation and push

The survey’s decision framework says a PWA is sufficient for content, commerce, booking, or an internal tool, with notifications as a secondary feature, and that a native app serves products that need background work, hardware over Bluetooth or NFC, App Store discovery, or notifications that must reach every user (WAVX solutions).

For install and push onboarding, the survey’s implementation guidance first shows iOS-specific instructions for using the Share menu and then presents push opt-in only when the app is running in standalone mode (WAVX solutions).

The survey cites iOS at 6.05% of mobile web usage in India in September 2026, while noting that urban and premium segments run higher (WAVX solutions).

Related entries on this site

• Capabilities: see capability reference.
• Performance: see performance guidance.
• Storage: see storage, quota, and persistence reference.

Open and unverified

• Whether the seven-day script-writable-storage rule applies unchanged across iPhone configurations is not confirmed.
• Whether notification display is mandatory for pushes across iPhone Web Push configurations is not confirmed.
• The per-version support status of Background Sync, Background Fetch, Web Bluetooth, Web NFC, and WebUSB was not independently device-tested.
• iOS mobile-web usage outside India in September 2026 is not quantified.
• Whether iOS 27 implements the full set of static-routing conditions and sources described by MDN is not confirmed.

Correction (2026-10-14)

Multiple installations have long been supported. iOS 16.4 added support for using the manifest id with the user-selected name to identify those installations and synchronize their settings (WebKit).

Sources

• PWAs on iPhone: What Works and What Does Not (October 2026) (dev.to)
• Web Push for Web Apps on iOS and iPadOS (webkit.org)
• WebKit Features in Safari 16.4 (webkit.org)
• Updates to Storage Policy (webkit.org)
• InstallEvent: addRoutes() method (developer.mozilla.org)
• BeforeInstallPromptEvent (developer.mozilla.org)