Four ways onto Google Play, compared by what actually happens in review
This comparison is organised around the question this site exists for: will it get listed, and what will Google ask of you along the way?
The options
WebView app. A native Android shell whose main screen renders your site in a WebView, with native extras (push, offline screen, menus). What the builder produces. Works for any website, including hosted platforms.
Trusted Web Activity (TWA). A shell that opens your site in the device's Chrome, full-screen, after you prove domain ownership. Requires the site to be a valid progressive web app (manifest + service worker at your root). Google's designed path for PWAs.
Progressive web app, no store. Installable from the browser on Android and iPhone; not on Play at all unless wrapped as a TWA.
Native / cross-platform. A separate codebase (Kotlin, Flutter, React Native). Not produced here.
Review and listing comparison
| WebView app | TWA | PWA only | Native | |
|---|---|---|---|---|
| Can be listed on Google Play | Yes | Yes | No | Yes |
| Minimum-functionality risk | Real; mitigated by push, offline, native nav | Lower; Google-endorsed pattern, still needs substance | n/a | Low |
| Works for Shopify / Wix / Squarespace / Blogger | Yes | No (they can't host a service worker) | Partially | Yes |
| Reaches iPhone users | No | No | Yes | With a second build |
| Uses Chrome's cookies/login | No (own cookie jar) | Yes | Yes | n/a |
| Content updates need a release | No | No | No | Usually |
| Digital goods payments | Play Billing required | Play Billing via Digital Goods API | Your web checkout | Play Billing |
| Physical goods / services | Your web checkout, allowed | Your web checkout, allowed | Your web checkout | Your checkout, allowed |
| Data safety form | Declare site + integrations | Declare site + integrations | n/a | Declare app |
| Annual maintenance | Rebuild for target API | Rebuild for target API | None | OS updates, SDK updates |
| Effort | Minutes + forms | Hours (PWA first) + forms | Hours | Weeks to months |
| Cost here | APK free; APK + AAB bundle US$5 | TWA test APK free (sister site); AAB via Bubblewrap/PWABuilder | Free | — |
Which one, by situation
"My site is on Shopify / Wix / Squarespace / Blogger and I want to be on Play."
WebView app. It is the only route that doesn't require hosting files at your domain root. Enable push, the offline screen and native navigation; follow the checklist.
"I host my own site and want Play presence with the least policy risk."
Make the site a PWA, then list it as a TWA. Google designed that pattern and reviewers know it. Our sister site FreeWebToApp covers the PWA side; the Play forms are the same and are covered here.
"I sell downloads, courses or subscriptions."
Any Play listing must use Play Billing for those. In a WebView app that means integrating Play Billing natively; in a TWA, the Digital Goods API. If your margins can't absorb 15%, a PWA installed from your site with your own checkout is the honest alternative — and it is not on Play. The payments guide goes through the edge cases.
"I need a distributable APK, not a store listing."
WebView app, APK output. Internal tools, kiosks, closed communities. No review at all.
"My product needs Bluetooth, background location or lock-screen widgets."
Native. Nothing web-based reaches those reliably, and we would rather say so than sell you a wrapper.
What we leave out on purpose
No column called "others" with invented prices. Competing wrapper services exist at various monthly fees and some bundle real support; whether that is worth paying for depends on you. This site's claim is narrower: the bundle is free and correct, and the guides tell you the truth about review.