How to Turn a Lovable App into an Android App and Publish It on Google Play

Lovable is one of the fastest ways to build a working web app from a prompt, but it only publishes to the web: your project goes live at yourproject.lovable.app or on your own domain. Lovable doesn't produce an Android app or upload anything to Google Play. To get your Lovable app onto Android phones as a real, installable app, you package the published site inside a native Android shell. This guide shows how to do that without code, what to change in your Lovable project first so it works well on a phone, and how to take it all the way to Google Play.

Your options for getting a Lovable app on Android

Wrapping the published URL is the approach most Lovable builders choose, because it keeps Lovable as the place you build: you keep prompting and publishing as usual, and the Android app always loads the latest version. You only rebuild the app when you change native things like the icon, splash screen or permissions. The trade-offs between a PWA and a wrapped app are covered in PWA vs WebView app.

Before you convert: 6 things to fix in your Lovable project

Most problems people hit with Lovable apps on Android come from things that work fine in a desktop browser. Fix these in Lovable before you build the app. You can ask Lovable's AI to make most of these changes for you.

1. Publish it on your own domain

Connect a custom domain in Lovable's publish settings before you build. The URL is what your Android app loads, and it's also used for App Links and your privacy policy. Using your own domain means you can move hosting later without shipping a new app, and it looks more trustworthy to Google Play reviewers than a lovable.app subdomain.

2. Check every screen at phone width

Lovable's Tailwind layouts are usually responsive, but dashboards, tables and wide modals often aren't. Open your published site on a phone (or in your browser's device mode) and click through every page. Watch for content hidden behind fixed headers or footers, horizontal scrolling, and buttons too small to tap. Anything that's wrong in the mobile browser will be wrong in the app too.

3. Use a login method that works inside an app

This is the most important one. Google blocks its sign-in page inside embedded WebViews and shows a 403 disallowed_useragent error instead, so a "Sign in with Google" button that works on your website can fail inside an app built from it. Before you publish, test your login inside the app, and offer email and password or a one-time email code as your main sign-in method. If your project uses Supabase or Lovable Cloud authentication, you can ask Lovable to add these.

4. Update your auth redirect and site URLs

If your project uses Supabase auth, check that your custom domain is set as the site URL and listed in the allowed redirect URLs. Otherwise, sign-up confirmation emails and password reset links can point to the old lovable.app address or a preview URL.

5. Decide where email links should open

Links in emails, such as magic links and password resets, open in the phone's browser by default, not in your app, so the user ends up signed in on the website instead. Two fixes: use a six-digit email code instead of a magic link, or set up Android App Links so links to your domain open directly in the app. For App Links, add an assetlinks.json file to your Lovable project's public/.well-known/ folder, using the fingerprint your app builder gives you. If you publish on Google Play, include the SHA-256 fingerprint from Play Console's App integrity page as well.

6. Hide what only makes sense on the web

"Download our app" banners, cookie popups aimed at desktop, and footer links to your own website look odd inside an app. You can remove them in Lovable, or leave the website unchanged and hide them only inside the app with custom CSS, which Capsule injects into every page of your app.

Step by step: turn your Lovable app into an Android app

1. 1

   Publish your Lovable project

   Click Publish in Lovable and copy the live URL, ideally on your custom domain. Don't use the editor preview link.

2. 2

   Create a new app in Capsule

   Paste the URL, upload your icon (PNG, JPG, SVG and HEIC all work) and choose a splash screen: your icon on a brand colour, or a full-screen image.

3. 3

   Set your app name, package name and colours

   Pick a package name under your own brand, like com.yourbrand.app. It's permanent once published. Set status bar and navigation bar colours for light and dark mode to match your Lovable theme.

4. 4

   Turn on only the features your app uses

   Enable photo library access if users upload images, camera or location if your app needs them, and notifications if you want push. Add a bottom tab bar with up to five of your main routes, like /dashboard or /settings, so the app feels native.

5. 5

   Build, install and test

   Run the build, install the APK on an Android phone, and test sign-up, login, uploads and any payment flows inside the app.

6. 6

   Publish on Google Play

   Upload the AAB to Play Console. New personal developer accounts must run a 14-day closed test with 12 testers first.

If your Lovable app takes payments

Many Lovable apps use Stripe. Payments for physical goods and real-world services, like bookings, deliveries or consulting, can keep using Stripe inside your Android app. If you sell digital content or subscriptions that unlock features in the app itself, Google Play's Payments policy generally requires Google Play's billing system for purchases made in the app. Read the current policy for your country before you publish, because this is a common rejection reason for SaaS-style apps.

Getting approved on Google Play

• Give reviewers a working test login under App access in Play Console. Lovable apps often put everything behind a login, and reviewers who can't get in will reject the app.
• Fill in the Data safety form based on what your app actually collects: accounts, analytics, uploaded files, payment details.
• Make the app feel like an app: a proper icon and splash screen, a bottom tab bar, and push notifications all help with Google's minimum-functionality rules.
• Plan for the closed test if your account is new. See the 12 testers, 14 days rule.

Our complete Google Play publishing guide covers the account, store listing sizes and every Play Console form in order.

Updating your app after launch

Because the app loads your published Lovable site, anything you change and publish in Lovable appears in the Android app right away, with no new build and no Play Store review. You only need a new build when you change the icon, splash screen, app name, colours, permissions or tab bar. Built something with Bolt or Replit too? The process is similar: see Bolt app to Android and Replit app to Android.