Do Progressive Web Apps Work on iOS? The Complete Guide for 2026

Progressive Web Apps promise the best of both worlds: build one web experience and have it work like an app on every device. 

On Android, that promise largely holds up. On iPhone, it's a different story.

Apple has made progress. Push notifications arrived in iOS 16.4. Storage policies improved in Safari 17. Safari 18.4 added Declarative Web Push and Screen Wake Lock. And with iOS 26, every site added to the Home Screen now defaults to opening as a web app.

But there are still significant gaps - especially for ecommerce brands that depend on their iPhone customers. 

No App Store distribution. No background sync. Limited push notification reach. And Apple still forces every browser on iOS to use its own WebKit engine, which means PWA capabilities are entirely at Apple's discretion.

This guide covers exactly what PWAs can and can't do on iOS in 2026, what it means for your business, and what your options are.

What Is a Progressive Web App?

A Progressive Web App is a website that uses modern browser APIs to deliver an app-like experience. 

The key technologies are service workers (for offline caching and push notifications), a web app manifest (which tells the browser how the app should look and behave when installed), and HTTPS.

When a user "installs" a PWA, they're adding a shortcut to their home screen that opens the site in a standalone window, without browser UI. 

There's no app store involved. The app loads from the web, and updates happen automatically whenever the developer pushes changes to the site.

PWAs work across platforms by default. The same codebase runs on Android, iOS, and desktop. That's the appeal: one build, every device.

What PWAs Can Do on iOS in 2026

Before getting into limitations, it's worth acknowledging what actually works. PWAs on iOS have come a long way, particularly over the last two years.

Home screen installation

Users can add any website to their iPhone home screen. It shows up as an icon, opens in standalone mode (no Safari toolbar), and appears in the app switcher. As of iOS 26, every site added to the Home Screen defaults to opening as a web app, even without a manifest file.

Push notifications

Since iOS 16.4 (March 2023), PWAs added to the Home Screen can send push notifications. Safari 18.4 introduced Declarative Web Push, a simplified mechanism that doesn't require a service worker.

App icon badges

The Badge API has been supported since iOS 16.4, letting PWAs display notification counts on their home screen icon (requires notification permission).

Offline caching

Service workers can cache assets and data for offline access. This works reliably for returning visitors, though storage policies apply (more on that below).

Screen Wake Lock

Since Safari 18.4, Home Screen web apps can prevent the device from dimming and locking the screen. Useful for recipe apps, dashboards, or any hands-free use case.

Improved storage

Safari 17 increased storage quotas to up to 60% of total disk space per origin (80% overall) and added support for the Persistent Storage API, which lets developers request protection from automatic eviction (though it requires notification permission to work).

Other capabilities

PWAs on iOS also support geolocation, camera/microphone access, WebAuthn for passwordless authentication, the Web Share API, and Canvas/WebGL for graphics.

What PWAs Still Can't Do on iOS

This is where the gaps become significant, particularly for ecommerce brands.

No App Store Distribution

You cannot list a PWA in the Apple App Store. Apple's App Store Review Guidelines require native binaries compiled in Xcode. Guideline 4.2 (Minimum Functionality) explicitly rejects "repackaged websites," and sub-guideline 4.2.2 targets "web clippings" specifically.

There's no official workaround. Google has Trusted Web Activity (TWA), which lets you publish a PWA to the Google Play Store. Apple has no equivalent.

This matters because App Store presence is a discovery channel. Without it, there are no ratings, no reviews, no search visibility, and no appearing in category rankings. 

For ecommerce brands, that's a significant miss, especially considering iOS captures 67% of global app spending despite holding only about 28% market share.

No Automatic Install Prompt

On Android, Chrome can show an automatic "Add to Home Screen" banner using the beforeinstallprompt event. Safari on iOS does not support this.

Instead, users have to know to tap the Share icon, scroll through the share sheet, find "Add to Home Screen," and confirm. 

Most people don't know this option exists, and even fewer will go through the steps. Developers can build custom banners to educate users, but the conversion rate on those instructions is low compared to a native install prompt.

Push Notifications Work, but Reach Is Limited

Push notifications technically work on iOS PWAs since iOS 16.4, but the practical reach is much smaller than native push.

Here's why:

• Home Screen only. Push only works when the PWA has been added to the Home Screen. Notifications don't work from Safari tabs.
• No silent push. You can't send data-only notifications that update content in the background, a common pattern in native apps.
• No background wake. Push notifications can't trigger background code execution the way they do in native apps.
• Reliability issues. Service worker push listeners may not trigger reliably after device restarts. Unexpected unsubscriptions can also occur.
• Multi-step opt-in. Users must first install the PWA to their Home Screen, then grant notification permission. Each step loses a chunk of your audience.

The numbers tell the story. When prompted, only about 16% of mobile users accept web push notifications, compared to 40-70% for native apps. But the real gap is bigger than that: most PWA users on iOS never get to the prompt in the first place because they haven't added the app to their Home Screen. 

When you factor in the full funnel (discovery, Home Screen installation, then permission grant), the reachable audience for PWA push is roughly 10-15x smaller than native push.

Native apps also get features PWAs can't access: Time Sensitive notifications that break through Focus Mode, Live Activities for real-time order tracking on the Lock Screen, and provisional notifications that deliver silently without requiring a permission prompt upfront.

No Background Sync

iOS does not support the Background Sync API, Periodic Background Sync, or Background Fetch for PWAs. None of these have a timeline for implementation.

In practice, this means your PWA can't update content in the background. When a user taps your app icon, they see whatever was cached the last time they had it open. 

A native app, by contrast, can pre-fetch fresh product data, update prices, and sync cart contents before the user even sees the screen.

No Bluetooth, NFC, or Hardware Access

In June 2020, Apple declined to implement 16 web APIs in Safari, citing fingerprinting and privacy concerns. 

The blocked list includes Web Bluetooth, Web NFC, WebUSB, Web Serial, Web MIDI, the Battery Status API, and several sensor APIs.

Apple's position hasn't changed as of 2026. While Chrome on Android supports many of these, PWAs on iPhone have no access to Bluetooth peripherals, NFC tags, USB accessories, or most device sensors beyond basic accelerometer and gyroscope.

For most ecommerce brands, this is a minor issue. But if your product involves connected hardware, in-store NFC, or peripheral devices, PWAs on iOS are a non-starter.

Storage Can Be Wiped

While Safari's storage quotas have improved, PWA data on iOS is still more fragile than native app data.

Safari uses a "least-recently-used" eviction policy. If the device is under storage pressure, cached data from less-frequently-visited origins gets deleted first. 

The Persistent Storage API (available since Safari 17) lets developers request protection from automatic eviction, but it requires notification permission to work.

What does this mean practically? If a customer adds items to their cart through your PWA but doesn't come back for a while, that saved cart could be gone when they return. 

A native app's storage persists until the user manually deletes the app.

No Geofencing or Background Location

PWAs can access the user's location in the foreground, but neither iOS nor Android supports geofencing or background location tracking in web apps. The W3C Geofencing API proposal has been abandoned.

For brands that use location-based triggers (store proximity alerts, local offers, location-aware marketing), a native app is required.

Apple Controls Everything Through WebKit

Here's the fundamental structural issue: every browser on iOS uses Apple's WebKit engine. Chrome, Firefox, Edge, Brave - they're all running WebKit under the hood on iPhone. That means PWA capabilities on iOS are entirely determined by what Apple's WebKit team chooses to support.

Despite the EU's Digital Markets Act and the UK CMA designating Apple with Strategic Market Status in October 2025, this hasn't changed in practice. 

iOS 18.2 technically allows third-party browser engines in the EU, but Apple's implementation through BrowserEngineKit creates so much friction that zero browsers have adopted it as of early 2026.

In other words, there's no competitive pressure pushing PWA capabilities forward on iOS. Apple decides the roadmap.

The EU Tried to Fix This. It Hasn't Worked Yet.

The regulatory story around PWAs on iOS has been dramatic but, so far, largely symbolic in its impact.

In February 2024, developers discovered that Apple had quietly removed PWA support in the EU in the iOS 17.4 beta. PWAs added to the Home Screen would open as regular Safari tabs instead of standalone apps. 

Apple said the change was necessary because "addressing the complex security and privacy concerns associated with web apps using alternative browser engines would require building an entirely new integration architecture."

About three weeks later, after intense backlash from developers, Open Web Advocacy, and the European Commission, Apple reversed the decision. PWA support was restored.

In April 2025, the EU fined Apple 500 million euros for DMA non-compliance related to browser engine restrictions. The UK CMA followed in October 2025 by designating Apple with Strategic Market Status and finding that Apple's browser engine requirements harm web app competition on iOS.

The regulatory pressure is real. But in terms of what you can actually build with a PWA on an iPhone today, nothing has materially changed. All browsers still use WebKit. The same limitations that existed before the DMA exist now.

PWA on iOS vs. Android: A Quick Comparison

If you're evaluating PWAs, the platform gap matters. Here's how iOS and Android compare:

The gap is clear: Android treats PWAs as first-class citizens with broad API support. iOS treats them as a limited subset of what the web can do, and Apple controls the boundaries.

What This Means for Ecommerce Brands

Technical limitations are only useful context if you understand the business impact. Here's how these gaps translate to real outcomes for ecommerce:

Fewer customers get your push notifications

The multi-step install-then-permit process on iOS means your push audience will be a fraction of what a native app delivers. For brands that rely on push for abandoned cart recovery, flash sale alerts, and restock notifications, that's a direct hit to re-engagement revenue.

You're invisible in the App Store

iOS users account for 67% of global app spending. If your brand isn't in the App Store, you're missing the primary way these high-value customers discover and install apps. There's no organic search visibility, no category ranking, no review-driven social proof.

Returning customers may find a blank slate

If a shopper doesn't visit your PWA for a stretch and the device is under storage pressure, their saved cart, browsing history, and preferences can get wiped. When they come back, it's like starting over. A native app's data persists until the user explicitly uninstalls.

Your app can't stay current in the background

Without background sync, a PWA can't update product listings, prices, or inventory while the user isn't looking at it. Native apps can pre-fetch content so the experience is fresh the moment the user opens the app.

Deep linking is typically less reliable

Driving users from an email, SMS, or social ad directly into a specific product page is harder with a PWA than a native app. Universal links and App Links in native apps typically handle this more consistently.

When a PWA Makes Sense (and When It Doesn't)

PWAs aren't bad. They're a legitimate technology with real strengths. The question is whether they're the right fit for your specific situation.

A PWA can work well if:

• You're running a content-heavy site (blog, news, documentation) where offline reading is the main value-add
• Your audience is primarily on Android, where PWA capabilities are strong
• You have a limited budget and need to improve your mobile experience quickly
• You want to test whether an app-like experience resonates with your audience before investing in a native build

A PWA falls short if:

• You're an ecommerce brand with high-value iOS customers who drive a meaningful share of your revenue
• Push notifications are central to your retention strategy (abandoned carts, restock alerts, loyalty programs)
• App Store presence matters for your brand credibility and customer acquisition
• You need reliable offline functionality for shoppers who browse intermittently
• You've built a complex storefront with integrations and customizations that you don't want to rebuild

The Better Path: Turn Your Website (or PWA) Into a Native App

For brands that have already invested in building a strong website or online store, there's a middle ground between building a PWA and paying for a custom native app from scratch.

MobiLoud takes your existing website and extends it into a native iOS and Android app. 

Everything on your site, including all your features, integrations, and customizations, works inside the app without any rebuilding. When you update your site, the app updates too.

What that gets you:

• App Store distribution. Your app is listed on the Apple App Store and Google Play, with full search visibility, ratings, and reviews.
• Native push notifications. With native opt-in flows, you get the full reach that PWA push can't deliver. Time Sensitive notifications, Live Activities for order tracking, and rich media support are all available.
• Persistent data and sessions. No storage eviction. Your customers' carts, preferences, and login sessions stay put.
• Full website parity. Every feature on your site works in the app. New site updates go live in the app automatically, without app store resubmission.
• Done-for-you service. MobiLoud handles the build, submission, and ongoing maintenance. You don't need a mobile development team.

How It Works

1. Book your strategy call. We'll discuss your goals, answer your questions, and assess fit.
2. Get your custom app preview. Our team builds a personalized preview of your native app. You'll see exactly how it looks, feels, and performs.
3. Launch in 30 days. We handle everything. Your app goes live on the App Store and Google Play while you focus on your business.

We've built 2,000+ apps for brands like yours.

Curious whether a native app makes sense for your brand? Book a free 30-minute strategy call to see a preview of your app. No commitment. Just see if it's the right fit for you.

FAQs: iOS PWAs

Do PWAs work on iPhone?

Yes. PWAs can be installed to the iPhone Home Screen, run in standalone mode, send push notifications (since iOS 16.4), cache content for offline use, and display app icon badges. However, they have significant limitations compared to native apps and compared to PWAs on Android, including no App Store distribution, no background sync, and no automatic install prompt.

Can you put a PWA in the Apple App Store?

No. Apple does not allow PWAs to be submitted to the App Store. The App Store Review Guidelines require native binaries, and Guideline 4.2.2 specifically blocks "web clippings." Google Play does allow PWA submissions via Trusted Web Activity (TWA), but Apple has no equivalent.

Do PWAs support push notifications on iOS?

Yes, but with limitations. Push notifications work for PWAs that have been added to the Home Screen (not from Safari tabs). They require explicit user permission, don't support silent push or background wake, and the reachable audience is roughly 10-15x smaller than native app push once you factor in the multi-step install process. Apple added Declarative Web Push in Safari 18.4, which simplifies the implementation but doesn't change these fundamental reach limitations.

Are PWAs as good as native apps on iPhone?

For basic content delivery, PWAs can be close. But for ecommerce and any use case that depends on push notifications, App Store visibility, background data sync, or hardware access, native apps are substantially more capable on iOS. The PWA capability gap between Safari (86/100) and Chrome on Android (97/100) reflects iOS-specific constraints that Apple has not addressed.

Will Apple improve PWA support on iOS?

Apple has made incremental improvements (push in iOS 16.4, Declarative Web Push in Safari 18.4, default web app mode in iOS 26), but the pace is slow and the most impactful gaps, like background sync, hardware APIs, and automatic install prompts, remain unaddressed. Regulatory pressure from the EU and UK hasn't yet translated into meaningful capability changes. Apple's WebKit monopoly on iOS means the company controls the timeline entirely.