Apple’s PWA Limitations Are Deliberate, Not Negligence – A Push to Keep Users in the App Store
Apple drops support for PWA’s in EU - Coffee Lounge - Wappler Community
iOS 17.4 and PWA
Apple reverses course on death of Progressive Web Apps in EU
Videos
type of web application that can be cached through network and works as a standard native app
I’ve been diving deep into Progressive Web Apps (PWAs) lately, and the more I explore, the more I’m convinced that Apple’s half-hearted support for PWAs on iOS isn’t due to oversight or technical limitations—it’s a deliberate strategy to steer users toward native App Store apps. Here’s why I think Apple is intentionally holding back PWAs to protect their 15-30% cut from in-app purchases and keep developers locked into their ecosystem.
The PWA Problem on iOS
PWAs are a game-changer for cross-platform apps. They’re fast, lightweight, and don’t require App Store approval, which means developers can bypass Apple’s strict guidelines and revenue-sharing model. But on iOS, PWAs feel like a second-class citizen compared to native apps. Safari’s limitations and Apple’s slow adoption of PWA features scream intentional sabotage rather than negligence. Let’s break it down:
Push Notifications Are Half-Baked: Apple finally added Web Push API support in iOS 16.4 (2023), but it’s clunky. You need to add the PWA to the Home Screen to even enable notifications, and they’re less reliable than native push notifications. Even in 2025, iPadOS still lags behind with limited support. If Apple wanted PWAs to shine, they could’ve implemented seamless push notifications years ago, like Android did. Instead, they’ve dragged their feet, making PWAs feel like an afterthought.
Adding PWAs to the Home Screen Is a Hassle: Installing a PWA on iOS requires users to navigate to Safari, hit the “Share” button, and select “Add to Home Screen.” It’s not intuitive, especially for non-tech-savvy users. Compare that to Android, where Chrome prompts you to install a PWA with a single tap. Apple could easily add a prominent “Install” button or auto-prompt for PWAs, but they don’t. Why? Because a smoother PWA experience might reduce the number of users downloading native apps from the App Store.
No Autoplay for Video or Music: Safari restricts autoplay for videos and music in PWAs, treating them like regular web pages rather than apps. This kills the seamless experience for apps like music players or TikTok-like feeds, where autoplay is a core feature. Native apps don’t face this restriction, giving them a clear edge. Apple’s excuse might be “user experience,” but it feels like a calculated move to make PWAs less appealing for media-heavy apps.
Transparent Status Bar and Landscape Lock Issues: Older iOS versions allowed PWAs to use a transparent status bar for a full-screen, app-like feel, but recent updates have broken this functionality. Similarly, locking a PWA in landscape mode is a no-go, unlike native apps that can control orientation effortlessly. These are small but critical details that make PWAs feel less polished on iOS, pushing developers to go native.
Storage Limits and Other Restrictions: Features like Bluetooth, NFC, or advanced camera APIs? Forget about it. Safari treats PWAs like websites, not apps, limiting access to hardware and native-like capabilities. Meanwhile, native apps have near-unlimited access to iOS features. Coincidence? I doubt it. Even if it is added to the desktop, it still has restrictions regarding landscape lock, when you simply want it to be in portrait mode or landscape, and I suspect that Android will also allow you such an option, but on the iPhone you can forget about this.
Why Apple Wants to Limit PWAs
The motive is clear: money and control. The App Store is a cash cow, with Apple taking a 15-30% cut of in-app purchases and subscriptions. PWAs let developers bypass this by using their own payment systems (like crypto or Stripe) and avoid Apple’s approval process, which can reject apps for things like “gambling-like” mechanics. By keeping PWAs less functional and harder to use, Apple nudges users toward native apps where they can enforce their rules and rake in profits.
The Bigger Picture
Apple’s approach isn’t just about revenue—it’s about ecosystem lock-in. If PWAs worked as smoothly as native apps, developers could build once for web, iOS, and Android, reducing reliance on Apple’s tools like Xcode and the App Store. This would weaken Apple’s grip on the app market. By making PWAs feel like a watered-down experience, they ensure users and developers stay within their walled garden.
What Can We Do?
Raise Awareness: Call out Apple’s tactics on platforms like Reddit and push for better PWA support.
Support PWA-Friendly Browsers: While Safari dominates iOS, browsers like Firefox or Chrome could push Apple to improve PWA support through competition (though iOS forces all browsers to use WebKit, which limits their flexibility).
Optimize PWAs for iOS: Developers can work around some limitations using tools like Next.js with next-pwa or Vite with vite-plugin-pwa, but it’s an uphill battle.
What do you think? Is Apple intentionally kneecapping PWAs to protect their App Store profits, or is it just slow progress? Have you run into similar frustrations with PWAs on iOS?