r/PWA • u/mtomweb • Feb 27 '24
Open Letter to Tim Cook: Sabotaging Web Apps Is Indefensible
r/PWA • u/mtomweb • Feb 27 '24
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?
r/PWA • u/mtomweb • Mar 01 '24
r/PWA • u/shrihariprakash • Sep 03 '26
A brand new day, and a brand new situation of Apple being an absolute jerk towards PWAs.
As of iOS 27 public beta 6, Safari now seems to blur the top of your web page with absolutely zero consent and no way of opting out🙂
Someone in a different thread said that setting “apple-mobile-web-app-status-bar-style” to default will kick the blur out. But no lol. The screenshot is from the exact same config and the app “re-added” to the Home Screen.
Has anyone managed to work around this at all yet?
r/PWA • u/kubli_the_dog • Jul 30 '26
You can wrap your PWA in a minimal app shell with a tool like PWA builder or Capacitor, then list it on the App Store and Play Store, once installed it opens the PWA in a web view. This setup offers heaps of advantages for developer experience including:
Faster updates
Don't wait on code reviews from Apple or Google, ship new code and bug fixes as fast as website updates. Once the App shell is approved you can continue to update the PWA without further reviews
Single codebase
Ship to IOS and Android without writing Swift or Java. No double work and new features ship twice as fast and stay in sync.
Smaller code bundles
A minimal App shell can be pretty small for faster installs. My IOS App shell is 1.7MB, much smaller than the average of around 40MB. Also, TS libraries are built to be small and load fast.
Better onboarding funnel
Many users drop off when you direct them straight to the App store, with a PWA you can start your onboarding in browser and direct them to the App store once they are invested.
Most of the issues with this setup can be resolved pretty easily:
Lacking native features
Capacitor lets you drop into native code when required, and provides libraries. I had to do this for auth and notifications on IOS
Slower page loads
Service worker cache and a Single Page App can mitigate or completely resolve this.
It doesn't feel native
Careful design, like the things mentioned in this post can get you 99% there.
Have you found any issues with this approach? I've built this app with this setup and it has worked great. If you find a bug I'll show you how fast I can push a fix 😉
r/PWA • u/Obvious_Set5239 • Jan 22 '26
I've polished my web app, and came up with these small, but important things that let your PWA feel more native
You need to be sure your app automatically refreshes itself of updates the content inside; or you need to provide a button inside UI to refresh the page, because on phones this gesture is the only way for user to refresh the page.
To prevent this gesture you need to set overscroll-behavior-y root style to none, or to contain
:root {
overscroll-behavior-y: none;
}Thanks the person in comments for suggesting this solution instead of JS
When user taps on a button and similar elements, the mobile browser highlights this element. It breaks the immersion. To prevent this behavior you need to add this style
button, a, label, input {
-webkit-tap-highlight-color: transparent;
}It's annoying when a user holds a finger on a random area in your app, and the browser suggest downloading or printing the page. To prevent this you need to run event.preventDefault() on any elements where it's not supposed to be, but allow only on images, videos, selected text etc.
function isInsidePWA() {
return window.matchMedia('(display-mode: standalone)').matches;
}
document.addEventListener('contextmenu', (e) => {
if (!isInsidePWA()) {
return;
}
if (e.shiftKey) {
return;
}
if (e.target.matches('a, img, video, audio, '
+ 'textarea:not([disabled]), '
+ 'input[type="text"]:not([disabled]), '
+ 'div.cm-content[contenteditable="true"] *'
)) {
return;
}
const selection = window.getSelection();
const selectedText = selection.toString();
if (selectedText.length > 0) {
return;
}
e.preventDefault();
});This code allows the default context menu on links, images, videos, audio, text boxes, and on selected text. I think on a regular web page this restriction feels very unfriendly and hostilely for the user, so I don't recommend doing it outside PWA. I also allow PC users to open the default context menu holding shift key
You can go further and add your own context menu for images, videos, text, etc
This is similar to context menu - it's annoying when you can accidentally select tabs, checkboxes etc, images etc. To prevent this you need to use user-select: none; style
body.pwa {
user-select: none;
-webkit-user-select: none;
.allow-pwa-select, .allow-pwa-select * {
user-select: text;
-webkit-user-select: text;
}
}On a regular page this behavior also feels hostile, so I recommend enabling it only for PWA. For this purpose I add "pwa" class to body on ui load
...
if (isInsidePWA()) {
document.body.classList.add("pwa");
}
...I allow selection using allow-pwa-select class on elements like error message, and tables. Also user-select doesn't have effect on textboxes, so we don't need to worry about excluding them - the user will be able to select text they just entered
r/PWA • u/Bubbly_Lack6366 • Jan 14 '26
So I have this web app for users to track subscriptions, before it worked fine in mobile but the app wasn't really friendly for mobile users, it's responsive but it doesn't look nowhere like an actual native app.
So I decided to spent few hours to actually make it looks like an actual native app, even use vibrations API of the browser in some places.
Happy with the results.
r/PWA • u/dannymoerkerke • Jan 02 '25
I created What PWA Can Do Today, a showcase of demos of what is possible with PWAs today.
It’s a PWA itself so you can install it to your device and see for yourself what’s supported.
r/PWA • u/[deleted] • Mar 22 '24
I love WalletConnect’s PWA onboarding for Web3Inbox
Try yourself at: https://app.web3inbox.com/
We don’t really need app stores these days.
There should be a mobile SDK for one click installing instead of going through a share menu though.
Hope to see it soon.
r/PWA • u/Born2Die007 • Sep 27 '25
After 10 years as a web dev (mostly JS + PHP), I finally shipped a personal project as a native iOS app. I wanted to share the approach I took and the trade-offs I ran into in case anyone else is considering going the hybrid route.
Stack & Choices
Capacitor JS: Discovered it a couple years ago. It basically wraps a web app in a native shell so you can deploy to iOS/Android.
Vanilla JS: Instead of React/Vue, I went framework-free. It gave me tighter control and kept things fast.
Tailwind CSS: Made styling + prototyping quick while keeping the final CSS bundle small (purge helps a lot when performance is critical).
This combo (vanilla JS + Tailwind) ended up being lightweight, simple, and performant enough for a hybrid app.
The App – OfflineTunes
It’s a music player that supports MP3, FLAC, etc. The unique feature is Finetunes: instead of regular playlists, your Next/Previous buttons turn into Approve/Deny controls. You can go through tracks one by one and:
Approve → mark favorites, bulk rate, add to playlists, or move files
Deny → delete from device to clean up your library
It’s been surprisingly effective for organizing large collections. Personally, I use it while driving. controlling it entirely from steering wheel buttons. App is still being actively developed so are fixes that needs to be made. Would love some feedback if anyone has the time.
Capacitor Trade-offs
App size: My actual PWA size is ~140KB gzipped and <400KB without, but the iOS build is 35MB+. That’s just the overhead of Capacitor JS and some Native plugins like accessing the filesystem i guess.
UI polish: Native iOS components feel buttery smooth with their spring physics + animations. Recreating that in web tech is hard. Even with custom components + libraries, it’s tough to match Apple’s native feel.
Performance: On the bright side, an optimized PWA app feels close to an unoptimized native app. For something like a music player, it’s “good enough.”
Memory limits: Apple enforces strict RAM limits on WebView apps compared to PWAs. For example, when transferring music remotely, chunks are buffered in memory until a full song is complete. Holding just a few songs in memory can crash the app since iOS aggressively kills WebViews that use too much RAM.
Would I recommend this route?
For small, personal projects, yes. For larger apps where design polish and animations are critical. probably not. Use Native or React Native
Feel free to ask any questions you have!
r/PWA • u/mastafied • Sep 02 '26
UPDATE (solved, then reverted — root cause found): The blur only hits web apps using apple-mobile-web-app-status-bar-style: black-translucent. Switching the meta to default removes it completely (users must re-add the app to the Home Screen — the meta is frozen at install). To keep the status bar matching your theme, add a real fixed 1px element at the very top with your background color — iOS samples its background-color (per u/dannymoerkerke's rules below; pseudo-elements are invisible to the sampler). We reverted anyway: prefers-color-scheme is frozen per process in standalone, so after an OS dark/light switch the status bar stays wrong-colored until relaunch. Living with the blur until Apple fixes either issue; Feedbacks are being filed.
We build a construction management PWA (baukompass.ai) that our field crews install to their home screens — so this hits us daily.
Since iOS 27 developer beta 5, the system draws a progressive blur over the top edge of standalone web apps. It's not sampling a toolbar and it doesn't react to scrolling — it blurs whatever pixels the page renders near the status bar, unconditionally. On our login screen even the language picker and the theme toggle get washed out (screenshots attached).
What we tried, all verified in the shipped bundle, all without effect:
Solid opaque header + a body::before backing plate behind the status bar, scoped via u/media (display-mode: standalone)
Same scoped via a JS marker (navigator.standalone) to rule out MQ quirks
theme-color — ignored entirely this cycle; apple-mobile-web-app-status-bar-style: black-translucent is deprecated anyway
The frustrating part: native apps got an escape hatch. iOS 27 changed the default scrollEdgeEffectStyle from .soft (progressive blur) to .hard, and native devs can pick either. PWAs got neither the new default nor any control — no CSS property, no meta tag, nothing in the Safari 27 beta release notes. Beta 8's "status bar might appear blurred" fix (179470940) is about a different bug; the PWA blur is unchanged.
Has anyone found a workaround, or filed a Feedback? Happy to dupe — will add our FB number in the comments.
r/PWA • u/zainul1996 • Oct 16 '25
Hey r/PWA 👋
You all have been incredible. I launched PWAStore.io one week ago, and most of the traffic and feedback came from this subreddit.
I wanted to share what has happened so far, what I’ve improved based on your input, and ask for more feedback and new submissions.
• 54 PWAs listed
• 1,000 visitors
• Countless feedback messages through email, Telegram, and Reddit
• Added caching and optimized performance by reducing shadows, blurs, and animations. This helped a lot of older Android users.
• Added push notifications and haptic feedback (yes, even on iOS - happy to share how).
• Polished the UI and UX to make the store feel more like a native app.
• Added a Share button that copies the link on desktop and uses the native Share API on mobile devices.
• Migrated from Playwright running on an overloaded EC2 instance to a CI/CD build that creates an Ubuntu image with Chromium and deploys on AWS Lambda. It now scales better and costs much less.
• Improved SEO and how links display when shared.
Several people reached out offering paid “traffic boosts” or “SEO promotion.”
I turned those down because they usually hurt organic growth in the long run.
I want PWAStore to grow naturally through real users, authentic submissions, and community input, not fake clicks.
1️⃣ 1-click installs that feel like a real app store experience - u/diekus
2️⃣ Better screenshot capture and optimization
3️⃣ My own blob storage for pre-optimized images to improve loading speed and reduce cost
4️⃣ More guides, articles, and a browser support page
5️⃣ Improved classification and discovery for apps
6️⃣ A locked section for 18+ content such as dating, gambling, and crypto - u/1ncehost
7️⃣ A way for users to review or rate apps, still thinking through how to keep it simple and genuine - u/beardyfpv
• Try out the site and let me know what feels off or confusing
• If you have a PWA, please submit it. I want this to be a true directory of what the web is capable of
• If you have thoughts on how app reviews or ratings should work, I’d love your input
• If you’re curious about the iOS haptic trick or Lambda setup, ask and I’ll share
🔗 Check it out here: https://pwastore.io
Thank you to everyone who tried it, gave feedback, or sent encouragement.
This subreddit and community played a huge part in shaping PWAStore, and I’ll keep building in public and improving it week by week.
Special thanks to those who gave feedback on the launch post: u/acmeira, u/nenadalm, u/noahpro99, u/future_pedi_md, u/diekus, u/paverbrick, u/beardyfpv, u/mastermog, u/demarcoPaul, u/Alternative_Love5050, u/mintybadgerme, u/jozefchutka, u/1ncehost
r/PWA • u/GenerateNamesForUs • Aug 25 '21
r/PWA • u/lisannevdl • Feb 15 '24
r/PWA • u/mwbender • Mar 31 '23
Hey all, long time PWA believer here. So much so, that we just built an app store just for PWAs. It's called Store.app.
Not trying to promote anything, as we just launched in "developer beta," but was hoping to start a convo with the community to gather feedback on how we can better serve web devs and help to bring PWAs mainstream.
Our goal is to provide web developers with the benefits that native app devs have had for years, namely: 1) 3rd party validation; 2) quality feedback loops from user reviews, and most importantly, 3) new organic users. We also plan to release open source documentation, design standards, and more.
Again, we believe PWAs are the future and we welcome any feedback!
r/PWA • u/kivylius • Apr 13 '26
r/PWA • u/fallaciousreasoning • Feb 24 '26
It'd be great if PWAs could trigger the install prompt on iOS!
Hola!
I am writing on behalf of the Microsoft Edge team with some exciting news! We are thrilled to announce that Dev Trial for the `Web Install API` is live on version M139! 🥳The Web Install API provides a way to democratise and decentralise web application acquisition, by allowing a web site to install a web app. This means end users have the option to more easily discover new applications and experiences that they can acquire with reduced friction. To read the most up-to-date explainer, click here.
Try the feature and share feedback
To try the feature, follow these steps:
Use a Chromium-based browser, such as Microsoft Edge or Chrome, and make sure the version is at least 139.0.3402.0 in Edge, or 139.0.7258.0 in Chrome.
In the browser, open a new tab and go to about:flags.
Search for "web-app-installation-api" in the search box.
Set the Web App Installation API flag to Enabled, and then restart the browser.
To see early demos that use the Web Install API (after enabling the flag), refer to this link!
This is a crucial moment in the development cycle of a new web API. I encourage you to try out the API and let us know any feedback about the shape and UX of Web Install! To share feedback, please open an issue on the MSEdgeExplainers repository.We hope you're as excited as we are to continue the install() journey, and eagerly await your comments, suggestions and ideas!
r/PWA • u/matthijsgroen • Oct 05 '24
I use the service workers in quite standard fashion (offline caching) but still really happy with the result.
Why: I liked a game from the app store, but it was fully ridden with mandatory app viewing what you could not 'pay off'. So decided to make my own version. It uses only 1 image (wood pattern) the rest is emoji, and css gradients. I use indexedDB for state management and storage.
The game get harder as you progress, by using a fibonacci like scale that decides difficulty, adjusts level templates. Then the templates get filled with random blocks, and then a solver will try to solve it, to prove the level is playable :-) So far it seems to 'surprise' people that the web can be this smooth :-)
The particles for the halloween ghosts can be a bit taxing sometimes, but you can switch 'seasonal theming' off in the settings.
The game: https://matthijsgroen.github.io/block-sort/
There is no tracking/cookies/ads, so I have no clue how many people are playing, but if there are issues they tend to find me regardless ;-)
The source code: https://github.com/matthijsgroen/block-sort
Some learnings:
Even in PWA mode you need to have an 'interaction' before you can enable sound.
Performance in PWA mode seems less on iOS than running the game in the browser. But you need the PWA mode for data to survive for more than 7 days :/
Updates to app name or logo are not delegated, people need to re-install, losing all their local data in the process.
The 'navigator.share' is easy to use.
I'm still on the fence if I should add some instruction for people how to add the game to the homescreen. What are your experiences with that?
It wasn’t mentioned in the keynote, but on the page listing all features coming to iOS 16, under Safari:
Web push notifications
Adds support for opt‑in notifications on iOS. Coming in 2023.
r/PWA • u/distractedperuser • Mar 30 '21
r/PWA • u/mtomweb • Aug 06 '25
r/PWA
•
u/Previous_Till5909
•
Dec 22 '25
Hey r/PWA! 👋
A few days ago I shared why I chose PWA over native for my shopping list app. A lot of you asked great follow-up questions about how to actually get a PWA into the app stores using WebView wrappers—so I wrote up everything I learned.

I put together a detailed walkthrough with actual code from my production app:
Covers:
Android TWA setup (build.gradle config, Digital Asset Links)
iOS WKWebView wrapper (Settings.swift, navigation handling)
Push notification setup for both platforms
All the gotchas that wasted my time so you don't have to
Android (TWA) — Surprisingly Easy
Trusted Web Activities = Chrome running your PWA without URL bar
Used PWABuilder to generate the project
Total Java code needed: literally 4 lines
Service workers, offline mode—everything just works
Time to first build: ~2 hours
iOS (WKWebView) — More Work, More Control
Started with PWABuilder template
Had to whitelist OAuth domains (Google Sign-In debugging was fun 🙃)
Push notifications need native Firebase (no web push in WKWebView)
Time to first build: ~1 day
Digital Asset Links timing — deploy your assetlinks.json BEFORE your first Play Store upload, or users see a URL bar
Google Play's 14-day rule — new apps need 20+ testers for 2 weeks before production access
iOS OAuth redirects — WKWebView + Google Sign-In = pain. Whitelist domains carefully.
Apple review skepticism — be ready to explain why your WebView app has "enough native functionality"
✅ Worth it:
95% of code is still the PWA
Updates deploy instantly (no store review for content)
One codebase, three distribution channels
App store discoverability is real
⚠️ The catch:
Initial setup: budget 1-2 weeks
iOS push needs native Firebase
Two small native codebases to maintain
The app is live if you want to see the end result:
🌐 PWA (instant, no install): chibicart.com
📱 How to join the Android Test:
Join the testing group: https://groups.google.com/g/awesometesters2025
Download the TWA: https://play.google.com/store/apps/details?id=com.chibicart.twa
🍎 iPhone users: The iOS app is live on the App Store, or see install instructions here: https://chibicart.com/install
It's a shopping list app with a Japanese manga/chibi art style. Free to use—would love feedback from fellow PWA devs on how the wrapper feels vs. the pure PWA experience!
Again, the complete guide with code snippets:
Happy to answer questions here too. What's stopping you from putting your PWA in the stores?
r/PWA • u/dannymoerkerke • Sep 02 '26
By popular demand, I added a capabilities page to What PWA Can Do Today, which lists all capabilities on one page and indicates for each one if it's supported on your device.
You can filter by support and search for capabilities.