WebView vs TWA vs native
| WebView app | TWA (Trusted Web Activity) | Native | |
|---|---|---|---|
| Works with any website | Yes | PWA only | — |
| Changes needed on your site | None | Manifest, service worker, assetlinks.json | Rewrite |
| Offline | Bundled files or offline screen | Via service worker | Full control |
| Native UI (tab bar, splash, push) | Yes | Limited | Yes |
| Shares Chrome cookies | No (own storage) | Yes | — |
| Google sign-in inside the app | Needs a workaround | Works | Works |
| Build time without coding | Minutes | Minutes–hours | Weeks |
How a WebView app works
The APK contains a small native shell — an Activity with a WebView filling the screen — plus your settings: start URL or bundled files, colours, icon, permissions. When the app opens, the WebView loads your site. The shell handles everything a browser normally would: the back button, file pickers, camera and location permissions, downloads, external links, pull-to-refresh and an offline screen.
Want to see the code? Our WebView app code generator outputs a complete MainActivity.kt, manifest and Gradle file you can open in Android Studio.
How a TWA works
A TWA opens your PWA in a full-screen Chrome custom tab. Chrome only hides the address bar if your domain proves it owns the app through /.well-known/assetlinks.json. Tools like Bubblewrap and PWABuilder generate a TWA project from your manifest. It's a good fit when your PWA is already polished and you want Chrome's cookies and sign-in to carry over.
Is your PWA ready?
A TWA needs a manifest with name, start_url, display: standalone and 192 and 512 px icons (ideally one marked maskable). Paste yours into the manifest.json validator to check. A WebView app doesn't need any of this — but a good manifest still helps Chrome users install your site.
Build a web app APK without Android Studio
- Hosted web app or PWA: paste the URL into Website to App.
- Static build (React, Vue, Svelte, plain HTML): zip the build output and use HTML & ZIP to APK Builder for a fully offline app.
- Set the name, icon and colour, tap Build and download the signed APK.
Detecting the app from your site
Sometimes you want your website to behave a little differently inside the app — hide a "Download our app" banner, for example. See the WebView detector for a tested JavaScript snippet.
Create your app now — free
No watermark, no card, no Android Studio. Pick what you're starting from:
Frequently asked questions
How do I convert a web app to APK?
Paste the web app's URL into Website to App, or zip its static build and use HTML & ZIP to APK Builder. Both produce a signed APK in minutes.
What is the difference between WebView and TWA?
A WebView app renders your site inside the app itself and works with any site. A TWA opens your PWA in Chrome and requires a manifest, service worker and Digital Asset Links.
Can I convert a PWA to APK?
Yes, either way. A WebView wrapper needs nothing from your PWA; a TWA uses your manifest and assetlinks.json.
Do PWAs work offline in an APK?
In a TWA, your service worker handles offline. In a WebView app, bundle the files (HTML/ZIP to APK) or rely on the app's offline screen.
Is a WebView app allowed on Google Play?
Yes, when it offers real functionality and isn't just a copy of someone else's website.