Guide
PWA vs native wrapper: what Google Play and the App Store actually require
November 17, 2026 · 6 min read

Neither Google Play nor the App Store accepts a plain PWA, so you need a native wrapper to appear in either store. A wrapper is a small app package around your web app, and your product inside it stays the same.
The stores differ in how strict they are about that wrapper. Google Play has a light, official option for PWAs, while Apple accepts web-based apps but reviews them more strictly. Below you will see what each store requires, side by side, so you know what to prepare.
First, two simple definitions
A PWA is a website that people install from the browser. It has a manifest, icons and usually a service worker for offline use, and it lives on the home screen without any store.
A native wrapper is a small Android or iOS app that shows your web app inside it. The wrapper adds what the stores need, such as an app ID, a store icon and access to some phone features, while your product stays your web app.
What Google Play requires
Google Play only accepts an app package, which for new apps means an AAB file. So a manifest or a link on its own is not enough.
Google does, however, support web apps well. Its light wrapper, the Trusted Web Activity (TWA), opens your PWA in Chrome, full screen and without an address bar. To hide that address bar, you prove you own the domain with Digital Asset Links.
- A signed AAB, with a package name you keep forever.
- A recent target Android API level. Google raises this every year.
- A Google Play developer account (US$25, one time).
- A privacy policy and a completed Data safety form.
- Enough real functionality to pass the minimum functionality policy.
Read what a Trusted Web Activity is for more detail, or the full guide to publishing a PWA on Google Play.
What the Apple App Store requires
Apple has no equivalent of the TWA. To appear in the App Store, your web app needs an iOS app around it, usually a native shell that shows the web app in a WebKit view.
- A signed IPA, built with Apple's tools on a Mac.
- An Apple Developer Program membership (US$99 per year).
- A distribution certificate and provisioning profile.
- An app that feels like an app, not a repackaged website (guideline 4.2).
- Privacy labels and, if you have accounts, in-app account deletion.
Because Apple reviews web content more strictly, that shell needs to feel like a real app. Read why Apple rejects wrapped web apps before you submit.
Side by side
- Plain PWA: no store listing, no review, free. Installed from the browser. Limited on iPhone.
- Android TWA: Google Play listing. Uses Chrome, so web features and login work as on the web. Light to maintain.
- iOS native wrapper: App Store listing. Needs Apple signing, a Mac build and stricter review.
- Fully native app: both stores, best device access, but a separate codebase and the highest cost.
Which one do you need?
Stay with a plain PWA if your users find you through search and are happy to use the browser. It is the cheapest option, because there is nothing to build or review.
Add store apps when your customers expect to find you in the stores, or when you want push notifications and a familiar home-screen icon on iPhone. Most web products can do this without rewriting anything.
Go fully native only if your product depends on deep device features the web cannot reach, since that means a second codebase. Our article do you really need a native app? helps you decide.
Where PWAtoApp fits
PWAtoApp creates those wrappers for you: Android APK and AAB, and iOS IPA, from your existing web app. It costs €49.99 once, with unlimited builds and release signing. You still need your own developer accounts, because each store makes its own approval decision.
FAQ
Can I put my PWA on Google Play without a wrapper?
No. Google Play needs an app package. A Trusted Web Activity is the lightest way to wrap a PWA for Play, and it keeps your web app as the single source.
Will Apple accept a PWA without a wrapper?
No. Apple's store only accepts iOS apps. On iPhone, a plain PWA can only be added to the home screen from Safari.
Do I need two codebases for Android and iOS?
No. Both wrappers load the same web app. You update the website once, and both apps show the change. You only rebuild when the app itself changes, such as the icon or app settings.
Ready to build for Android and iOS?
€49.99 once includes unlimited Android APK and AAB plus iOS IPA builds, all from one dashboard.
Build my app