The short answer. A PWA is your web app installed from the browser: no store, no review, one codebase, updates the moment you deploy. On iPhone it now opens as a web app from the Home Screen and can send push notifications, but users have to add it themselves from the share menu, and it is not in the App Store. A wrapped web app gets you into the App Store and Google Play with the same code, but Apple asks for more than “a repackaged website.” A native app costs a rebuild and gives you everything the platform offers. Choose PWA for tools people use occasionally, a wrapper for store presence with little change, and native when the app is the product.
What is a PWA?
MDN: “A progressive web app (PWA) is an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app.” And: “it can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps.”
In practice a PWA is your existing web app plus a web app manifest (name, icon, colours) and a service worker (offline caching, background work where the browser allows it). Nothing goes through an app store. The same URL serves desktop, iPhone and Android.
PWAs on iPhone in 2026
Installing. web.dev: “A browser prompt to install your PWA doesn't exist On iOS and iPadOS.” Users add the app with Safari’s share menu and Add to Home Screen. Since Safari 26, WebKit says: “By default, every website added to the Home Screen opens as a web app.” It opens full screen with its own icon.
Push notifications. WebKit, February 2023: “Now with iOS and iPadOS 16.4, we are adding support for Web Push to Home Screen web apps.” The same release added the Badging API for the number on the icon. Push works only after the user has added the app to the Home Screen.
What you still do not get. No App Store listing, so no store search traffic or ratings. Some device features are not available to web apps in Safari: Apple has said of Web NFC, “We oppose this feature and will not implement it.” MDN marks Web Bluetooth, Web NFC and Background Sync as “not Baseline because it does not work in some of the most widely-used browsers.” Home Screen widgets, Live Activities and Apple Watch apps are native features.
PWAs on Android, and on Google Play
Installing. Chrome on Android installs a PWA as a WebAPK. web.dev: the installed app will “Have an icon in the app launcher and home screen” and “Appear on Settings, Apps.” Chrome can show an install prompt, unlike Safari.
Google Play. A PWA can be published on Google Play as a Trusted Web Activity. Android Developers: “Trusted Web Activity is a new way to open your web-app content such as your Progressive Web App (PWA) from your Android app using a protocol based on Custom Tabs.” Google’s Bubblewrap tool and Microsoft’s open-source PWABuilder generate the Android project. You need a Google Play developer account (US$25 once), and new personal accounts must run a 14-day closed test with 12 testers before release.
The middle option: wrap the web app for the stores
A wrapper builds a native app that loads your web app in a WebView and adds native features such as push notifications, biometric login and in-app purchases. Capacitor does this as an open-source project you run yourself; services such as Median, Despia, Natively and Appilix do it for you. Website to app converters compared lists eight of them with prices.
The trade-off is App Store review. Apple’s guideline 4.2: “Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or "app-like," it doesn't belong on the App Store.” A wrapper that only shows the website is the case this rule describes. The interface inside stays the web app’s: scrolling, gestures and navigation behave as they do in the browser.
When native is worth the rebuild
A native app is written in each platform’s language, Swift and SwiftUI on iPhone and Kotlin and Jetpack Compose on Android, and uses the platform’s own components. It is worth the rebuild when:
The app is the product and users open it every day.
You need features outside the web. Widgets, Live Activities, Apple Watch, background tasks, Bluetooth, NFC, or a local database for real offline use.
You want the platform’s interface. Native navigation, gestures, text sizes and dark mode, the way users expect them on each phone.
You need the App Store and the wrapped version would not pass guideline 4.2.
The usual objection is cost: two codebases. With an AI agent writing the code, that cost is lower than it was. Modaal builds a SwiftUI app and a Jetpack Compose app from one project, with each feature’s logic written once and shared, on the AI subscription you already have. The Free plan covers one project on one platform; Pro (€9 per user per month billed annually) builds both and adds TestFlight and automated App Store publishing.
How to choose for your web app
Choose a PWA when people use the app occasionally (a booking flow, a dashboard, an internal tool), you do not need the stores, and you want to deploy changes instantly. Add a manifest and a service worker, and show iPhone users how to add it to the Home Screen.
Choose a wrapper when you need App Store and Google Play listings soon, the web app already works well on a phone, and you can add native features such as push notifications to pass review.
Choose native when the app is the product, needs device features or native feel, or you plan to maintain it for years.
You can also move through all three in order: a PWA to validate, a wrapper for first store presence, and a native rebuild once the app earns it. Convert a web app to a mobile app covers the rebuild route step by step.
PWA vs wrapped web app vs native app
| PWA | Wrapped web app | Native app | |
|---|---|---|---|
| How users get it | Browser: Add to Home Screen (iPhone), install prompt (Android) | App Store and Google Play | App Store and Google Play |
| Store listing | No (Google Play possible as a Trusted Web Activity) | Yes | Yes |
| Code | Your web app | Your web app in a native shell | Swift (iPhone) and Kotlin (Android) |
| Updates | Instant on deploy | Web content instant; shell needs store releases | Store releases |
| Push on iPhone | Yes, after Add to Home Screen (iOS 16.4+) | Yes | Yes |
| Widgets, Live Activities, Watch | Native features only | Only with native code added | Yes |
| Bluetooth, NFC on iPhone | NFC not in Safari; Bluetooth not Baseline on the web | Through native plugins | Yes |
| App Store review | None | Guideline 4.2 applies | Standard review |
| Cost to start | Lowest | Low to medium | A rebuild |
From WebKit, web.dev, MDN, Android Developers and Apple’s App Review Guidelines, read 28 October 2026.
Keep reading
- What is a WebView app?
The wrapper route, explained.
- Do you need a mobile app?
A 4-step check before you build.
- Website to APK
Package a PWA as an Android app with PWABuilder or Bubblewrap.
- Website to app converters compared
Eight wrappers, with prices and who publishes.
- Native app vs web app
The broader comparison.
- Convert a web app to a mobile app
The three routes from a web app to the stores.
Native iPhone and Android apps. Start free.
One project, two native apps: Swift for iPhone, Kotlin for Android.
