To publish a Lovable app on Google Play you package the hosted web app as a native Android App Bundle (AAB), register a Google Play developer account (one-time USD 25), complete the Data safety form and listing, and pass review. New personal developer accounts currently also have to run a closed test with at least 12 testers for 14 days before production access, so plan at least two to three weeks.
On this page
Google Play is usually the easier of the two stores for a Lovable project. The review is less strict about web-based apps than Apple's, the developer fee is a one-time payment and Android WebViews are based on Chromium, so a Lovable app tends to render exactly as it does in Chrome. The friction lies elsewhere: account verification, the closed testing requirement for new personal accounts and the policy forms that Google now enforces carefully. This guide focuses on those Android-specific steps.
Choose the right developer account type
Google Play distinguishes between personal and organization developer accounts. Both pay the same one-time USD 25 registration fee and both require identity verification, but they differ in one important way. New personal accounts currently must run a closed test with at least 12 opted-in testers for 14 consecutive days before they can apply for production access. Organization accounts, which require a D-U-N-S number and business verification, are not subject to this rule at the time of writing.
If your Lovable app is a business product, register as an organization. It looks more trustworthy on the store listing, it avoids the tester requirement and it keeps the app owned by the company rather than a founder's private account. If you are a solo builder with a personal account, read our explainer on the Google Play closed testing requirement and recruit testers early.
Turn the Lovable web app into an Android App Bundle
Google Play only accepts Android App Bundles (.aab) for new apps, signed with an upload key, with Play App Signing managing the final distribution key. Lovable does not produce that file, so you need a native Android project that loads your app. A template like WebViewGold gives you that project in Android Studio: you enter your Lovable production URL, set the package name, icon, splash screen and colors, switch on native features and generate a signed bundle.
Android-specific details are worth checking before you build. The hardware back button should navigate back inside your app instead of closing it. File uploads from forms need the WebView's file chooser to work, otherwise profile photo uploads silently fail. External links such as payment pages or help articles should open in a Custom Tab or the browser, while your own domain stays inside the app. Make sure the target API level meets Google's current requirement, which rises every year.
Step by step: Play Console submission
- Register in the Play Console, pay the USD 25 fee and complete identity or organization verification.
- Create the app, choose default language, app or game, free or paid, and accept the declarations.
- Upload the signed AAB to an internal testing track first and install it on a few real devices.
- Fill in the App content section: privacy policy, app access with demo credentials, ads declaration, content rating questionnaire, target audience and the Data safety form.
- Create the store listing: app name (max 30 characters), short description (80), full description (4000), 512 x 512 icon, 1024 x 500 feature graphic and phone screenshots.
- For a new personal account, promote the build to closed testing, keep at least 12 testers opted in for 14 days, then apply for production access.
- Roll out to production, ideally as a staged rollout to a percentage of users.
The Data safety form for a Supabase-backed app
The Data safety form asks what user data your app collects, whether it is shared with third parties, whether it is encrypted in transit and whether users can request deletion. A Lovable app typically collects at least an email address and user IDs through Supabase Auth, plus any content users create. Add the data collected by analytics, crash reporting and push notification SDKs in the native shell. Google compares your answers with the app's behavior and its SDKs, and inconsistencies can lead to rejection or a policy warning later.
Google also requires an account deletion option both inside the app and as a web link listed in the Play Console if users can create accounts. Ask Lovable to generate a public deletion request page on your domain in addition to the in-app setting. This is a small task that regularly blocks first submissions.
Android-specific quality checks
Google's review is lighter on web-based apps than Apple's, but policies against apps that only display a website still exist, and low-quality listings rank poorly. Test on a mid-range device, not only a flagship, because heavy JavaScript bundles feel slower there. Check behavior with no network: a native offline screen is far better than the default WebView error page. Confirm that push notification permission is requested at a sensible moment, since Android 13 and later require runtime permission. Our article on making a WebView app feel native covers performance work that pays off on Android in particular.
After approval
Updates to your Lovable frontend appear in the Android app as soon as you publish them, while native changes need a new bundle with a higher version code. Use Android vitals in the Play Console to watch crashes and ANRs, and reply to reviews, which influences how the listing converts. If you are shipping iOS too, follow our companion guide on publishing a Lovable app on the Apple App Store, since the stricter Apple review should shape your feature set for both platforms. Teams that want someone to handle accounts, forms, testers and review replies can hand the publishing process to AppSubmitter. And when a Lovable app starts to turn into a real business, our custom development and company building team helps take it from working product to operating company.
Frequently asked questions
How much does it cost to publish a Lovable app on Google Play?
Google charges a one-time USD 25 developer registration fee. Your other costs are the native wrapper or development work, hosting for the Lovable app and any third-party services you use.
Can I upload an APK instead of an AAB?
Not for new apps on Google Play. New apps must be uploaded as Android App Bundles. APKs remain useful for direct testing on devices outside the store.
Do I need 12 testers for my Lovable Android app?
Currently only if you publish from a personal developer account created after Google introduced the rule. Organization accounts are not subject to the 12 testers for 14 days requirement at the time of writing.
Does the Android app update when I change my Lovable project?
Yes, web content updates instantly because the app loads your hosted frontend. Changes to the native shell, permissions or SDKs require a new bundle and review.