How to Publish a Lovable App on Google Play
Short answer: To publish a Lovable app on Google Play, wrap the deployed web app in a native Android shell, build a signed Android App Bundle, and release it through the Play Console after closed testing and the Data safety form. Google is generally more permissive than Apple, but new personal developer accounts face testing requirements that can add weeks if you do not plan for them.
On this page
The short answer: Android is a packaging and process problem
A Lovable project is a web application, usually React and Vite on the front end with Supabase behind it. Android cannot install that from the Play Store as is. You need an Android app that hosts your web app, adds native capabilities, and is uploaded as a signed Android App Bundle (.aab). A native wrapper like WebViewGold for Android gives you an Android Studio project where you set the start URL, package name and features, then build the bundle.
Compared with iOS, the technical hurdle on Android is lower. The real work sits in the Play Console: account verification, testing tracks, store listing, content rating, the Data safety section and target API level compliance. Teams that treat these as a checklist launch smoothly; teams that discover them on submission day lose weeks.
Account type matters more than most founders expect
Google Play charges a one-time 25 USD registration fee. The bigger decision is whether you register as a personal or an organization account. Google has introduced stricter rules for new personal accounts, including a mandatory closed test with a minimum number of testers over a minimum period before you can apply for production access. The exact thresholds have changed over time, so check the current requirement in the Play Console help before you plan your launch date.
Organization accounts require a D-U-N-S number and identity verification, which takes time upfront but usually avoids the closed-testing gate. If your Lovable app is a company product, register the company. It also keeps the app listing tied to the business rather than one person, which matters when you raise money or sell.
Building the Android App Bundle
Whatever wrapper you choose, the build steps look similar. Keep the signing key safe: losing it is one of the few truly painful mistakes on Android.
- Open the WebViewGold Android project in Android Studio and set your production URL, a unique package name such as com.yourcompany.app, the app name and brand colors.
- Configure the adaptive icon (foreground and background layers) and the splash screen so the app does not look like a browser on first launch.
- Enable the native features your product needs: Firebase push notifications, file uploads, camera, offline fallback page, external link handling.
- Set the target SDK to the level Google currently requires for new apps and updates, and test on at least one older and one current Android version.
- Generate an upload key, enroll in Play App Signing so Google holds the app signing key, and build a release .aab.
- Test the release build on physical devices, not only the emulator, focusing on the back button, keyboard overlap and file pickers.
Need a hand? WebViewGold helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.
Android-specific details Lovable apps often miss
The hardware back button is the classic one. Users expect it to navigate back inside your app, not close it. React Router-based Lovable apps handle history well, but the wrapper must pass the back gesture to the WebView and only exit on the start screen.
Second, Android WebViews handle file inputs differently from Chrome. If users upload avatars, receipts or documents to Supabase Storage, verify the picker opens camera and gallery correctly. Third, Google sign-in is blocked in embedded WebViews by Google's own policy, so use a native sign-in flow or open the OAuth step in a Custom Tab. Fourth, check that deep links from emails, for example password resets, open the app through Android App Links with a verified assetlinks.json on your domain.
The Play Console checklist
Before you press the review button, every item below should be complete. The Console shows a task list, but it does not explain what reviewers actually look for.
- Store listing: short description up to 80 characters, full description, feature graphic 1024 x 500, phone screenshots, optional tablet screenshots.
- Content rating questionnaire answered honestly for the app's real content, including user-generated content.
- Data safety form matching what your app and its SDKs actually collect, including Supabase auth data, analytics and crash reporting.
- Privacy policy URL that is public and names the app and the data it handles.
- Account deletion: if users can create accounts, provide an in-app path and a web URL for deletion requests.
- App access instructions with test credentials so reviewers can get past the login screen.
- Target audience and ads declaration, especially if any part of the audience could be under 18.
Release strategy: testing tracks and staged rollouts
Use the tracks Google provides. Internal testing is instant and ideal for your team. Closed testing gives you real feedback from invited users and, for new personal accounts, is required before production. When you go live, start with a staged rollout to a small percentage of users and watch Android vitals for crashes and ANRs before expanding.
Because the wrapper loads your Lovable web app, most fixes ship through your normal web deployment. Reserve new bundles for native changes. That combination of fast web iteration and controlled native releases is the main reason WebViewGold-style wrappers suit Lovable products. If you want someone to handle the Console work, testing tracks and any policy emails in your own account, appsubmitter.io offers exactly that, and a free call is a quick way to find out what your app still needs.
Frequently asked questions
Is Google Play easier than the App Store for a Lovable app?
Technically yes, review is usually faster and less strict about apps that load web content. Procedurally it can be slower for new personal accounts because of the mandatory closed test before production access. Organization accounts with complete verification usually move faster. Either way, policy compliance on data safety and account deletion is enforced.
Can I upload an APK instead of an App Bundle?
For new apps on Google Play, the Android App Bundle format is required. You can still build APKs for direct testing on devices, but the Play Console expects an .aab for releases. Enrolling in Play App Signing is part of that process, and Google then generates optimized APKs for each device configuration.
Do I need a separate Android codebase for my Lovable app?
No. A native wrapper hosts your existing Lovable web app, so the product logic stays in one place. The Android project only contains configuration and native features such as push notifications, file handling and deep links. You maintain it occasionally, mainly for target API level updates and new native capabilities.
