Deploy & App Stores
How to Publish a Lovable App on Google Play (Step-by-Step Guide)
To publish a Lovable app on Google Play, sync the project to GitHub, add Capacitor's Android platform, build a signed Android App Bundle (.aab) in Android Studio and release it through Play Console. If your developer account is a new personal account, you must also run a closed test with at least 12 testers for 14 days before Google lets you go to production.
What do you need before starting the Android build?
You need the Lovable code in GitHub, a Google Play developer account and a machine with Android Studio. Unlike iOS, Android builds run on Windows, macOS or Linux, so any team member can do it.
Decide early whether you register as an organization or a personal account. Organization accounts need a D-U-N-S number but are not subject to the closed-testing requirement for new personal accounts.
- Google Play Console account (25 USD one-time registration) with identity verification completed
- Android Studio with a recent SDK and JDK
- Lovable GitHub sync enabled and the repo cloned locally
- A package name you will never change, such as com.yourcompany.yourapp
How do you add Android to a Lovable project with Capacitor?
Capacitor treats the Vite dist folder as the app's web content and generates a standard Gradle project around it. The Android project should be committed to the repo so build settings survive future Lovable edits.
If you already wrapped the app for iOS, reuse the same capacitor.config.ts; only the platform folder is new.
- npm install @capacitor/android
- npm run build to produce the dist folder
- npx cap add android, then npx cap sync android
- npx cap open android to open the project in Android Studio
- Set applicationId, versionCode and versionName in the app-level build.gradle
- Confirm compileSdk and targetSdk meet Google Play's current target API level requirement
How do you produce a signed Android App Bundle?
Google Play only accepts new apps as Android App Bundles, so you build an .aab, not an APK. Use Build > Generate Signed Bundle in Android Studio and create an upload keystore.
Enroll in Play App Signing: Google holds the app signing key and you keep only the upload key. Back up the keystore and its passwords in a password manager; losing the upload key means a support request to reset it, and a keystore that only exists on one laptop is a real business risk.
- Increase versionCode for every upload, or Play Console rejects the bundle
- Use a release build with minification tested, not just debug builds
- Store keystore credentials outside the Git repo
How do you get through the 12 testers, 14 days requirement?
New personal developer accounts must run a closed test with at least 12 opted-in testers who stay opted in for 14 consecutive days before applying for production access. Plan this into your launch date; it is the single biggest timeline surprise for Lovable builders.
Use the waiting period productively. Real testers on real Android devices find the issues Lovable's browser preview never shows: back-button behavior, keyboard overlap and older Android WebView versions.
- Upload the first .aab to the Internal testing track to check it installs
- Create a Closed testing track and add testers via an email list or Google Group
- Share the opt-in link and confirm at least 12 people actually opt in and install
- Ship updates during the 14 days and collect feedback
- Apply for production access in Play Console and answer the questions about your testing
What should Android users experience that differs from the web version?
The app should respect Android conventions, which a Lovable web UI does not do by default. The hardware or gesture back button is the most important: handle it with Capacitor's App plugin so it navigates back in your React router instead of closing the app.
Supabase OAuth needs the same deep-link treatment as on iOS. Configure Android App Links with an assetlinks.json file on your domain, or a custom scheme, and add the redirect to Supabase's allowed URLs. Google sign-in on Android feels best with a native credential plugin rather than a web popup.
- Edge-to-edge layout with correct status bar and navigation bar insets
- Push notifications via Firebase Cloud Messaging and the Capacitor Push Notifications plugin
- Android 13+ notification permission prompt at a sensible moment
How do you fill in the Data safety form and store listing?
Declare every type of data your Lovable app and its SDKs collect, how it is used and whether it is shared. Supabase means you at least process account info such as email and user IDs; add anything stored in your tables like names, photos or location.
The form must match your privacy policy and actual behavior, and Google also requires a way for users to request account deletion, both inside the app and via a web link listed in the Data safety section.
- Content rating questionnaire (IARC) and target audience declaration
- App access instructions with test credentials if login is required
- Feature graphic, phone screenshots and a short and full description
- Payments: digital goods sold in-app generally require Google Play Billing
Should you do it yourself or bring in specialists?
Doing it yourself is realistic for a simple Lovable app; payments, push and deep links are where projects stall. Our AI Code Engineers at neooutput handle Capacitor setup, signing and Play Console for Lovable apps, and appsubmitter.io helps teams with the store submission side.
Whichever route you choose, start the closed test as early as possible because the clock is fixed.
If your Lovable app is already live on the web and you mainly need a store presence, WebViewGold is a no-code alternative to a Capacitor project: it wraps the deployed web app in a native Android (and iOS) shell with configurable push notifications, deep links and an offline screen. A wrapper still has to feel like a real app, so plan native touches such as push and offline handling; if you also target iOS, Apple's guideline 4.2 rejects pure website wrappers without native value.
Frequently asked questions
Can I upload an APK instead of an AAB?
Not for new apps on Google Play. New apps must be published as Android App Bundles; you can still build APKs for direct testing on devices.
Do organization accounts need 12 testers too?
The 12-testers-for-14-days requirement applies to personal developer accounts created after Google introduced the rule in late 2023. Organization accounts are currently not subject to it, but they need business verification.
Can I reuse my iOS Capacitor setup for Android?
Yes. The same web build and capacitor.config.ts serve both platforms; you only add the Android platform and its native configuration such as signing, permissions and Firebase.
How long does Google's review take?
Review times vary from hours to several days, and first submissions and new accounts often take longer. Build buffer time into your launch plan.
