# Turn your web app into a Google Play app with a TWA

> Publish your PWA on Google Play as a Trusted Web Activity: Bubblewrap or PWABuilder, assetlinks.json, signing keys, and the 12-tester rule for new accounts.

By Tommy Pham · 2026-11-14 · https://tommydev.web.app/blog/pwa-to-google-play-twa

**Short answer:** if your web app is a PWA (it has a manifest, icons and HTTPS), you can publish it on Google Play as a **Trusted Web Activity (TWA)**: an Android app that opens your site full-screen in Chrome with no browser bar. Generate the package with **PWABuilder** or **Bubblewrap**, prove you own the site with an `assetlinks.json` file, and upload it to Play Console. New personal developer accounts must first run a closed test with **12 testers for 14 days**.

Two apps I was lead developer on use this approach: the Google Play listings for [Pocket Party](/work/pocket-party) and [Imposter Games](/work/imposter-games) are TWA packages (the package names end in `.twa`), wrapping the same web apps people play in the browser.

Part of my [launch guide](/blog/launch-vibe-coded-app).

## Why use a TWA instead of rebuilding natively?

- **One codebase.** Every web deploy updates the Android app instantly, with no store review for content changes.
- **Real Play Store presence**: a listing, search, reviews and installs.
- **Full Chrome engine**, so your PWA's features (service worker, push, offline) keep working.

The limits: it's still your web app. Deep native features (background services, some hardware APIs) need native code. And Play billing for digital goods needs the Digital Goods API, not your web checkout.

## What does my PWA need first?

- **HTTPS** on your own domain.
- **A web app manifest** with `name`, `short_name`, `start_url`, `display: "standalone"`, a theme color and icons (192px and 512px, plus a maskable icon).
- **A service worker.**
- **Chrome's installability criteria met, and good performance.** (Lighthouse dropped its PWA category in 2024, so check installability in Chrome DevTools → Application → Manifest.) Google Play still reviews the app's quality.

## How do I generate the Android package?

**Option A: PWABuilder** (easiest). Go to [pwabuilder.com](https://www.pwabuilder.com), enter your URL, choose Android, and download the package. It uses Bubblewrap under the hood and gives you a signed bundle (`.aab`), a signing key and an `assetlinks.json` file.

**Option B: Bubblewrap CLI** (more control, scriptable):

```bash
npm i -g @bubblewrap/cli
bubblewrap init --manifest https://yourapp.com/manifest.webmanifest
bubblewrap build
```

Either way, **keep the signing key and its passwords somewhere safe.** You need them for every update.

## How do I prove I own the website?

Digital Asset Links tells Android that your app and your domain belong together. Without it, the app shows a browser address bar, which is the most common TWA problem.

Host this at `https://yourapp.com/.well-known/assetlinks.json`:

```json
[{
  "relation": ["delegate_permission/common.handle_all_urls"],
  "target": {
    "namespace": "android_app",
    "package_name": "com.yourapp.twa",
    "sha256_cert_fingerprints": ["AA:BB:..."]
  }
}]
```

**The catch:** Google Play re-signs your app with its own key (Play App Signing). After the first upload, copy the **SHA-256 fingerprint of the app signing key from Play Console's App integrity (App signing) page** and add it to the file. You can list both your upload key and Play's key. If the browser bar still appears, check the file with Google's [Digital Asset Links tester](https://developers.google.com/digital-asset-links/tools/generator).

## What's the 12-tester rule?

Google Play requires **personal developer accounts created after November 13, 2023** to run a **closed test with at least 12 opted-in testers for 14 continuous days** before applying for production access. Organization accounts (registered with a D-U-N-S number) are generally exempt. Plan for it: recruit testers early, and don't pause the closed track, which can restart the clock.

## Other Play Store requirements to plan for

- **Target API level.** Google Play requires new apps and updates to target a recent Android API level, and the minimum rises every year. Update Bubblewrap or PWABuilder and rebuild before the deadline.
- **Store listing**: screenshots, a feature graphic (1024x500), a privacy policy URL and the data safety form.
- **Content rating** questionnaire.
- **Developer verification**: identity and, for organizations, business details.

## FAQ

### Can I publish to the iOS App Store the same way?

No. Apple doesn't support TWAs, and an app that only wraps a website risks rejection under guideline 4.2 (minimum functionality). For iOS you need a native or React Native app. → [Shipping an Expo app to the App Store](/blog/expo-app-store-submission)

### Do updates need Play review?

Changes to your website appear in the app immediately. Changes to the Android package (icon, name, target SDK) need a new upload and review.

### Can I use Stripe inside a TWA?

For physical goods and services, yes. For digital goods and subscriptions, Google Play's payments policy generally requires Play Billing, which TWAs reach through the Digital Goods API. Check the current policy for your category.

---

Want your web app on Google Play? I've done it for production apps. See [my work](/#work) or get in touch below.

## Sources

- Chrome for Developers: [Trusted Web Activity quick start](https://developer.chrome.com/docs/android/trusted-web-activity/quick-start)
- Google Play Console Help: [App testing requirements for new personal developer accounts](https://support.google.com/googleplay/android-developer/answer/14151465)
- [PWABuilder](https://www.pwabuilder.com) and [Bubblewrap on GitHub](https://github.com/GoogleChromeLabs/bubblewrap)
- Checked November 2026