Key takeaways
- Lovable has no Android export. Your routes are a WebView wrapper, a Trusted Web Activity, Capacitor for older single-page projects or a native rebuild.
- WebViewGold for Android, made by our team, adds push, file uploads, App Links, biometrics and Google Play Billing to your Lovable URL without writing Kotlin.
- Play Console sets the timeline: personal accounts created after November 13, 2023 need a closed test with 12 opted-in testers for 14 days before production.
- Google sign-in must leave the WebView (Custom Tabs or native sign-in), digital goods need Play Billing, and account deletion needs an in-app option plus a web link.
Our recommended solution
Turn your Lovable app into a real Android app with WebViewGold
WebViewGold wraps the Lovable web app you already have in a native Android Studio project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at Google Play look for. Built by our own team, and we submit WebViewGold apps all the time.
How do you convert Lovable to an Android app?
You convert Lovable to an Android app by packaging the web app Lovable publishes – ideally on your own domain – into an Android project, adding native features and releasing it through your own Google Play Console account. Lovable doesn't generate Android code: its FAQ recommends a PWA or wrapping the published URL "with a tool such as Capacitor outside Lovable".
A lot of apps start that way now. The Stockholm company raised USD 400 million at a USD 13.3 billion valuation in its Series C on August 12, 2026, and the Android app it launched in April 2026 is a builder for editing projects on the go – not a way to put them on Google Play.
Google looks at a wrapped app from a slightly different angle than Apple. Besides basic functionality, its policies ask whether you own the website you show and what data leaves the device, and Play Console enforces account testing and API levels before anything reaches review. If you also plan an iPhone version, our Lovable to App Store guide covers Apple's side.
WebView, TWA or Capacitor: which Android route fits a Lovable project?
| Route | What your Lovable project must provide | Google sign-in | Selling digital goods | Best for |
|---|---|---|---|---|
| WebView app with WebViewGold | The published URL on your domain | Handed to a Chrome Custom Tab, or native sign-in | Google Play Billing through WebViewGold's In-App Purchases API (Extended license) | Most Lovable apps that need native features |
| Trusted Web Activity (Bubblewrap, PWABuilder) | A real PWA – manifest and service worker you add yourself – plus a Digital Asset Links file on your domain | Works, because the app runs in the user's browser | Needs extra web-side integration | Teams who already maintain a PWA |
| Capacitor, built yourself | Older React + Vite projects: the dist/ build. Newer TanStack Start projects need their server | Native plugin | Native plugin | Developers who maintain Android Studio projects |
| Native rebuild (Kotlin or React Native) | Lovable Cloud as the backend | Credential Manager | Play Billing Library | Apps with heavy offline or device needs |
A TWA is the lightest option on paper: Android shows your PWA full screen in the user's browser and checks ownership through Digital Asset Links. If that check fails, the browser falls back to a Custom Tab with visible browser UI. Lovable's hosting docs don't mention service workers, so the PWA part is yours to add and maintain. Our PWABuilder alternative comparison covers TWA tooling in depth.
Capacitor can bundle the static dist/ folder of an older Lovable project. Projects created since May 13, 2026 render on the server, though, and Capacitor's own configuration reference says loading a live URL through server.url is "not intended for use in production". That leaves a WebView app built to load a live URL as the practical default.
Want your Lovable app in Google Play without the trial and error?
Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.
Play Console groundwork that sets your launch date
- Developer account. Register a personal or an organization account; Google charges a one-time registration fee. Organization accounts need a D-U-N-S number, and new personal accounts must verify a physical Android phone in the Play Console app.
- Closed testing for personal accounts. Accounts created after November 13, 2023 need a closed test with at least 12 testers who stay opted in for 14 consecutive days before they can apply for production. Internal testing doesn't count. Our closed testing guide shows how to pass on the first attempt.
- Package name. Package names on Google Play are permanent, so choose it carefully – for example
com.yourcompany.yourapp. - Android App Bundle. New apps have had to publish as AAB since August 2021.
- Play App Signing. Google holds the app signing key and you sign uploads with your upload key. Note the app signing key's SHA-256 fingerprint – Digital Asset Links needs it.
- Target API level 36. Since August 31, 2026, new apps and updates must target Android 16 (API level 36), as our target API guide explains. Targeting 36 also switches on predictive back and edge-to-edge display, so test both.
Building the Lovable Android app with WebViewGold, step by step
WebViewGold for Android is a ready-made Android Studio project from our own team: a one-time purchase whose free updates track Google Play's target SDK requirements. You own the project and publish it in your own Play Console.
- Set the start URL to your primary custom domain. A paid Lovable plan gives you the domain, and the
lovable.appaddress makes it harder to show Google that app and website belong together. - Add app mode. Give the app a custom user agent and let Lovable hide web-only parts such as the site footer and install prompts when it sees your marker – presentation only. Cookie consent you need for EU users stays in place, restyled for the app or handled natively.
- Use native navigation. The built-in Material navigation drawer and Material 3 bottom bar need no changes to your website. Then test the back gesture: it should step back through your Lovable screens and only leave the app from the start screen.
- Wire up push with Firebase Cloud Messaging, OneSignal or Pushwoosh, triggered from a Lovable edge function. Android 13 and later require the
POST_NOTIFICATIONSruntime permission – ask at a meaningful moment through WebViewGold'sregisterpush://link instead of on first launch. - Check uploads. A plain WebView ignores
<input type="file">until the app implements a file chooser. WebViewGold handles file and camera uploads, including multiple files, and its document scanner adds a "Scan document" option that hands your web app a PDF. - Add App Links so links to your domain open the app. They need
/.well-known/assetlinks.jsonon your domain, and Android requires the file to load without any redirect. Declare your primary domain, because Lovable sends other connected domains – includingwwwby default – there with a 302. After publishing, open the URL and confirm it returns the JSON file. - Handle offline with WebViewGold's offline screen and a "Try again" button through the Reconnect API, instead of Chrome's error page.
- Finish the native layer: Google Play's native review dialog, biometric unlock with BiometricPrompt, a QR scanner where your app needs one and, optionally, Firebase Crashlytics.
- Build a signed AAB, upload it to internal testing for a first check and then to your closed test.
No Android Studio? WebViewGold's Cloud Builder builds the project in your browser, or our team sets it up for you.
Lovable sign-in on Android: what changes inside a WebView
Email with password and the one-time codes Lovable can send work inside the app. Magic links are the weak spot: the email app opens them in the browser, so the session lands outside your app unless App Links route the link back in. For Google's reviewers, enter working credentials in the App access declaration of Play Console's App content section. Create that account in Lovable under More → Cloud → Users → Add user → Create new user – accounts created there are confirmed automatically.
Google sign-in needs more care. Google's OAuth policy forbids directing a sign-in request to "an embedded user-agent under the developer's control", and a request from a WebView fails with disallowed_useragent. Two compliant options:
- Chrome Custom Tabs. Google recommends Custom Tabs on Android. WebViewGold's
googlelogin://prefix opens the Google URL in a Custom Tab, and your OAuth redirect brings the user back. Lovable's redirect URLs accept custom schemes such asmyapp://callback– test the full round trip on a real device. - Native sign-in. Sign in with Google through Android's Credential Manager and pass the result to your web session. That is custom native code in the Android Studio project.
Phone sign-in through your own SMS provider behaves like on the web. Apple's rules on login services don't apply on Google Play, but the OAuth part does on both stores – our article on login rejections in WebView apps covers it from the iOS side.
The shortcut from Lovable to Google Play
WebViewGold: your Lovable app, native on Android
Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:
- Push notificationsOneSignal or Firebase, for real, personal events
- Native offline screenNo browser error pages when the connection drops
- Native splash screenApp-like start instead of a loading web page
- Deep linksLinks open the right screen inside the app
- QR & barcode scannerDevice features the website alone can't offer
- In-app purchasesNative purchase flows where the store requires them
No tool guarantees an approval: Google still judges what your app offers. Use the native features in your main user journey and keep proving that you own the website – our App Specialists review your WebViewGold app before it goes to Google Play.
Google Play policies a wrapped Lovable app has to pass
| Policy | Lovable-specific risk | What to do |
|---|---|---|
| Webviews and Affiliate Spam | The lovable.app site in a frame, with nothing linking the website to your developer account | Your own domain, matching developer details, Digital Asset Links and native features – see the WebView spam guide |
| Broken functionality | A blank screen because the Lovable backend paused when credits ran out; upload fields that do nothing; a back gesture that closes the app | Watch credits during review and test uploads and back navigation – see the broken functionality guide |
| Data safety | Lovable Cloud stores account data and user content, AI features send text to model providers, push SDKs add identifiers | Declare the app, its SDKs and the web content you control – see the Data safety guide |
| Account deletion | Lovable's Delete user is an admin tool only | An in-app delete option plus a public web page, linked in the Data safety form – see the account deletion guide |
| Payments | Paddle or Stripe checkout for premium features | Google Play Billing for digital goods; Stripe or Shopify for physical goods and services. Regional alternative billing programs exist, each with its own conditions |
| Deceptive behavior | Generated claims the app doesn't keep, or features that stay hidden | Make listing and app match reality – see the deceptive behavior guide |
Closed test, production access and updates from Lovable
The closed test is where Lovable's speed pays off: when testers report a bug in the web part, you fix it in Lovable and publish – no new build needed. Ship native updates during the test as well. Google tells developers to act on feedback, and a test with one build on day one and nothing after looks like a test nobody ran. Keep a short log of feedback and fixes; the production access questions ask for exactly that.
After 14 days with at least 12 opted-in testers, apply for production from the Play Console dashboard. Google says it takes more time to review apps from certain developer accounts, which can mean review times of up to seven days or longer in exceptional cases (Play Console Help). Once approved, start with a staged rollout.
After launch, the rule is simple: what you publish in Lovable reaches Android users immediately, while new permissions, SDKs or native modules need a new AAB with a higher versionCode – and an updated Data safety form whenever the data changes. If the same project runs as an iOS app, keep new features out of production until Apple has reviewed the build that describes them. Our article on Lovable apps rejected under Guideline 5.6 explains why.
Getting the Google Play submission done – with or without help
appsubmitter.io handles the parts of Google Play that cost the most time: a CI/CD pipeline that produces signed release AABs, upload key and Play App Signing setup, the store listing, the Data safety form, guidance through closed testing and the production access application, and the communication with the Google Play review team. Everything happens in your own Play Console account. Code changes – native Google sign-in, for example – aren't part of the package; we quote them upfront when your project needs them. And nobody can promise an approval: Google decides.
See what the Android submission service includes, book the Google Play package or start with a free consultation call about your Lovable app.
Checklist before you submit
- The app loads your primary custom domain, and assetlinks.json on that domain lists the Play app signing SHA-256 fingerprint.
- Personal accounts: the closed test has at least 12 testers who stayed opted in for 14 consecutive days.
- The release is a signed Android App Bundle that targets API level 36.
- Back gesture, file uploads and the notification permission prompt work on Android 13 and later.
- Google sign-in opens in a Custom Tab or runs natively – never inside the WebView.
- App access in Play Console contains working reviewer credentials.
- The Data safety form covers the app, its SDKs, Lovable Cloud and any AI providers.
- People can delete their account in the app and through a public web page linked in the Data safety form.
- Digital goods use Google Play Billing; Stripe or Paddle only sell physical goods or services in the app.
Frequently asked questions
Do I need Android Studio to convert Lovable to an Android app?
Can I use a Trusted Web Activity for my Lovable app instead of a WebView?
How long does Google Play review take for a new app?
Do I really need 12 testers before my Lovable app can go live?
Can my Lovable app keep using Stripe or Paddle on Google Play?
Do changes I publish in Lovable reach Android users without an update?
Recommended solution
From Lovable to Google Play: WebViewGold + appsubmitter.io
- 1 Build with WebViewGold Turn your website into native iOS and Android projects.
- 2 Add native value Push, offline screen, deep links or scanning in your main flow.
- 3 We submit it Our App Specialists submit and talk to the review team.
WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.
Sources and further reading
- Lovable Docs – FAQ (native apps, PWA, Capacitor)
- Lovable – Series C announcement (August 12, 2026)
- Lovable Docs – Users and authentication
- Lovable Docs – Add payments to your app
- Google for Developers – OAuth 2.0 policies (embedded user-agents)
- Play Console Help – App testing requirements for new personal developer accounts
- Play Console Help – Publish your app (review times)
- WebViewGold for Android – documentation
Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.