Deploy & App Stores

How to Publish a v0 (Vercel) App on Google Play

For Google Play, a v0 app has an extra option that iOS lacks: a Trusted Web Activity that runs your Vercel-hosted Next.js app full-screen in Chrome, verified with a Digital Asset Links file. If you need more native features, use Capacitor with a static export instead. Either way you ship a signed .aab through Play Console and, on a new personal account, complete a 14-day closed test with 12 testers.

neooutput editorial team 3 min read Auf Deutsch lesen

Should a v0 app use a Trusted Web Activity or Capacitor on Android?

Use a Trusted Web Activity if your v0 app is a good PWA and mostly needs reach; use Capacitor if you need deep native integrations or offline-first behavior. A TWA keeps all Next.js server features working because it loads your live Vercel deployment.

Google Play accepts TWAs as long as the app provides real value and meets its quality and policy requirements.

  • TWA: full Next.js on Vercel, Chrome rendering, web push, small app size
  • Capacitor: static export, native plugins, bundled UI, more setup
  • WebView wrapper such as WebViewGold: native features without code

How do you build a TWA for a v0 app?

Generate an Android project with a tool such as Bubblewrap from your web app manifest, then prove domain ownership with a Digital Asset Links file. On Vercel you serve it from the public folder at the .well-known path.

If the assetlinks.json fingerprint does not match the signing key Google uses, the app shows a browser address bar, a common source of confusion. With Play App Signing, use the SHA-256 fingerprint from Play Console, not only your upload key.

  1. Add a complete web app manifest and icons to the v0 project
  2. Generate the TWA project from the manifest URL
  3. Add public/.well-known/assetlinks.json with the Play App Signing fingerprint
  4. Deploy to Vercel and verify the file is served
  5. Build the signed .aab and upload it to internal testing

How do you go the Capacitor route instead?

Split the v0 app into a static frontend for the app and API routes that stay on Vercel. Configure CORS and token-based auth so the Android app can call your APIs from its own origin.

Then add the Android platform with Capacitor, open it in Android Studio and build a signed bundle. Check that targetSdk meets Google Play's current requirement.

How do you handle the closed testing period?

If your account is a new personal account, keep at least 12 testers opted into a closed test for 14 consecutive days. Start this the moment the first stable build exists.

A TWA has an advantage here: most UI fixes deploy to Vercel instantly without a new app version, so testers always see the latest version. Still upload at least one improved build to show iteration.

What Android-specific features should a v0 app add?

Add the integrations that make the app worth installing over the website. For TWAs that usually means web push notifications delegated to Android notifications and an offline page via a service worker; for Capacitor, Firebase Cloud Messaging and native plugins.

Make sure Android App Links open your app from search results and emails, which reuses the same assetlinks.json file.

  • Back navigation that matches user expectations
  • Edge-to-edge layout and correct theme color
  • Google Play Billing for digital goods sold in the app

How do you complete Data safety and the listing?

Declare all data your Next.js backend, Vercel analytics and any third-party services collect. For a TWA, data the website collects through the app counts too.

Add app access credentials if login is needed, complete the content rating questionnaire and provide account deletion in-app and via a web link.

What is the smartest next step?

Pick your architecture, then start the closed test as early as possible. neooutput's AI Code Engineers build TWA and Capacitor setups for v0 apps, and appsubmitter.io supports the Play Console submission.

Frequently asked questions

Does a TWA work with Next.js server components?

Yes. A TWA loads your live Vercel deployment in Chrome, so server components, API routes and middleware work exactly as on the web.

Why does my TWA show a URL bar?

Digital Asset Links verification failed. Usually the SHA-256 fingerprint in assetlinks.json does not match the Play App Signing key or the file is not served at the right path.

Can I use the same app for iOS?

TWAs are Android-only. For iOS you need Capacitor, a WebView wrapper or a native rewrite.

Does Google Play accept TWA apps?

Yes, many Play Store apps are TWAs. They must still meet Play's policies and provide genuine value beyond a simple website shortcut.

All insights