Publish a Lovable App to Google Play: TWA, Wrapper and Testing Rules

How to publish a Lovable app on Google Play: Trusted Web Activity vs native wrapper, Supabase login on Android, closed testing rules and Play policies.

Short answer

A Lovable app reaches Google Play as an Android App Bundle that loads your deployed React app, built either as a Trusted Web Activity or as a native wrapper such as WebViewGold. The wrapper gives you more native features and control; a TWA is lighter but needs Digital Asset Links on your domain. Plan for Google's closed testing requirement on new personal accounts, the Data safety form and account deletion.

On this page
  1. Android is friendlier, but not automatic
  2. Two Android-specific options
  3. The wrapper route, step by step
  4. The TWA route, briefly
  5. Testing requirements you cannot skip
  6. Play Console paperwork for a Lovable app
  7. Making it more than a website
  8. Release and maintenance
  9. FAQ
  10. Tools from the jocapps ecosystem

Android is friendlier, but not automatic

Google Play is generally more open to web-based apps than Apple. That does not mean anything goes. Play's policies on spam and minimum functionality still reject apps that are a thin copy of a website, and new developer accounts face testing requirements before they can publish at all.

A Lovable project gives you a React front end, often with Supabase behind it, published on a Lovable domain or your own, with code synced to GitHub. Lovable does not produce an Android App Bundle. You create one around your deployed app.

Two Android-specific options

Android offers a route iOS does not: the Trusted Web Activity (TWA). A TWA shows your website full screen using the user's Chrome (or another supporting browser), without browser UI, as long as your domain proves it belongs to the app.

Trusted Web ActivityNative wrapper (WebViewGold)
RenderingUser's browser engineAndroid System WebView inside your app
Login sessionsShared with the browserApp's own storage
Google sign-inWorks, since it runs in the browserMust use the system browser or a native flow
Native featuresLimited to web APIs (web push, share)Push, offline screens, file handling, 40+ native APIs
Domain requirementassetlinks.json on your domainNone
Control over UXDepends on browser behaviourFull control in the app project

For a content-first Lovable app that is already a good PWA, a TWA can be enough. For most products with login, uploads, notifications and a need to feel like an app, a native wrapper is the more predictable choice and also works for the iOS version later.

The wrapper route, step by step

  1. Harden the web app for phones. Test on a mid-range Android device in Chrome first. Check the virtual keyboard covering inputs, the system back gesture and tap targets.
  2. Use a custom production domain. The app's start URL must not change.
  3. Build the Android app. WebViewGold offers an Android Studio project template: insert the Lovable URL, set package name, icon, splash screen and colours, enable push notifications, offline handling and other native features. You build a signed App Bundle. One-time purchase, and the project stays yours.
  4. Handle the back button. Android users expect the hardware or gesture back action to navigate inside the app, not to close it. Make sure your React routes work with history navigation.
  5. Sort out authentication. Supabase email login works inside the web view. Google sign-in does not, because Google blocks OAuth in embedded web views; open it in a Custom Tab or the browser and return to the app via a deep link.
  6. Add account deletion. Google Play requires apps that allow account creation to offer account deletion in the app and via a web link you enter in the Play Console. With Supabase, an edge function can delete the auth user and related rows.

If you prefer someone else to do steps 3 to 5, WeSetupYourWebViewApp sets up the WebViewGold app for you, including full source code, in about 72 hours.

The TWA route, briefly

If you choose a TWA, you need a web app manifest with name, icons and theme colour, ideally a service worker, and a file at /.well-known/assetlinks.json on your domain containing your app's package name and signing certificate fingerprint. In a Vite project such as Lovable's, files in the public folder are served from the site root, but confirm in a browser that the URL returns the JSON and not your app's 404 page. Use the fingerprint of the Play App Signing key from the Play Console, not only your upload key, or verification fails and the app shows a browser address bar.

Testing requirements you cannot skip

If your Google Play developer account is a personal account created after November 2023, Google requires a closed test with a minimum number of testers who stay opted in for a continuous period (currently 12 testers for 14 days) before you can apply for production access. Organization accounts are not subject to this rule, which is one reason to register as a company. See developer accounts for companies.

Even without the requirement, use internal testing and closed testing tracks. Our guide to TestFlight and Play Console internal testing explains the setup.

Play Console paperwork for a Lovable app

  • Data safety form. List what Supabase stores (account data, uploaded files, messages) and what analytics you run. Be accurate; mismatches with actual behaviour lead to enforcement.
  • Privacy policy URL. Hosted on your domain, matching the app.
  • Content rating questionnaire. Answer for user-generated content if users can post.
  • Target API level. Google raises the required target API level every year. Updates to WebViewGold help, but you must ship updates to keep the app available to new users.
  • Payments. Digital goods and subscriptions consumed in the app generally need Google Play Billing; physical goods and real-world services can use Stripe.

Making it more than a website

Google's minimum functionality policy targets apps that add nothing over the browser. Push notifications for real events, file downloads that land in the right place, camera uploads, an offline screen and a native-feeling navigation are typically enough to show value. Our article on Google Play rejection reasons for converted web apps lists the most frequent issues and fixes.

Release and maintenance

Upload the App Bundle, roll out to a closed track, then to production in stages. appsubmitter.io handles store listings, submissions and rejection replies in your own Play Console, and sets up CI/CD if you release often. When the app grows beyond a wrapper and needs real native screens, apprat.io builds and maintains Android and iOS apps with AI-assisted development plus human developer hours.

If you are still designing the stack, our explainer on the Lovable and Supabase stack covers the production hardening that pays off on mobile too.

FAQ

Can I publish a Lovable app as a PWA on Google Play?

Yes, through a Trusted Web Activity, if your domain serves the Digital Asset Links file and the app meets Play's quality expectations. For login-heavy apps with native features, a wrapper is usually more robust.

Why does Google sign-in fail in my Lovable Android app?

Google blocks OAuth sign-in in embedded web views. Run the Google flow in a Custom Tab or the browser and return to the app, or use email login.

Do I need 12 testers to publish my Lovable app?

Only for personal developer accounts created after November 2023. Organization accounts are exempt, but closed testing is still worth doing.

Do changes in Lovable require a new Play Store release?

No, the app loads your live web app. Native changes such as new permissions, push configuration or a new target API level require a new bundle.

Tools from the jocapps ecosystem

Want this done right, and fast?

Talk to our AI Code Engineers and AI architects. In a free 30-minute call we look at your idea, prototype or roadmap and tell you honestly what it takes to ship it.

24/7 call support in English and German.

Free call

Free intro call

Tell us which task an AI agent should take responsibility for. We show how our platform, AI Code Engineers and operations plug into your stack.

  • 30 minutes, no obligation
  • Honest feasibility check
  • Concrete next step
Rather talk now? 24/7 call support in English and German+49 761 519 751 50