Create Free APK

AI app builders · Lovable

Lovable to APK: turn your Lovable app into an Android app

You built the app in Lovable and it works in the browser. Here is how to get it onto phones as a real Android app, installable from a file or from Google Play, without rewriting a line of it.

Short answer. Publish your project in Lovable, copy its .lovable.app (or custom domain) address, and paste it into the free APK builder. The same free build gives you the AAB file Google Play asks for. If you want the code shipped inside the app instead, connect Lovable to GitHub, download the repository as a ZIP and import it in AppMint.

Lovable writes React with Vite, TypeScript, Tailwind and shadcn/ui, and uses Supabase for the database, sign-in and storage when you turn that on.

Two ways to build it

RouteBest forWhat happens
Wrap the published URLMost Lovable apps, especially ones that use SupabaseThe app loads your live Lovable site. Every change you publish in Lovable shows up in the app with no rebuild.
Build the exported codeApps that should open offline or ship their own filesSync the project to GitHub, download the ZIP, import it in the AppMint app. The React build runs on your phone and the result is packed into the APK.

Step by step

  1. Publish the project in Lovable

    Open the project, press Publish and wait for the address. It looks like your-app.lovable.app. If you connected your own domain, use that instead: it is the address your users will see if a page ever shows it.

  2. Check the site on a phone first

    Open the published address in Chrome on an Android phone. What you see there is what the app will show. Fix anything that only looks right on a laptop (a table wider than the screen, a sidebar that never collapses) in Lovable before you build.

  3. Paste the address into the builder

    Go to the APK builder, paste the address, give the app a name and an icon, and download the APK. You get the APK and the AAB for Google Play in the same free build.

  4. Or build from the code

    In Lovable, connect GitHub from the project settings. On GitHub, use Code → Download ZIP. In AppMint, choose the ZIP option and pick that file. If your code reads import.meta.env.VITE_… values (your Supabase URL and anon key, usually), AppMint adds a step that lists each one so you can fill them in.

What works inside the app

  • Supabase email and password sign-in, sessions that survive closing the app, and row-level security, because the app is running your real site.
  • Google sign-in: the Google and Supabase sign-in pages open inside the app, so the user comes back signed in instead of landing in Chrome. See Google sign-in.
  • File uploads from the photo library or camera, and the microphone for voice notes. When you give AppMint your site address it scans the site's scripts and ticks the camera, microphone and location permissions the site actually uses.
  • Routes from React Router, including the back button: back goes to the previous screen of your app, and closes an open dialog first.

What to check first

Stripe checkout for digital things

Google Play requires Play Billing for digital goods and subscriptions sold inside an app. A Lovable app that sells a subscription with Stripe can be rejected. Physical goods and services are fine. The options are in in-app purchases.

Preview links are not your app

The editor preview address changes and needs you signed in to Lovable. Always build from the published address.

Unpublishing breaks the app

A wrapped app shows whatever the address serves. If you unpublish or rename the Lovable project, installed apps show an error. Keep the published version live, or use a custom domain so you can move hosts later.

Environment values in a code build

In a ZIP build, a VITE_ value you leave empty is built as undefined. The Supabase anon key is meant to be public; a secret key never belongs in front-end code, in the browser or in an app.

Publishing your Lovable app on Google Play

Google Play takes an AAB (Android App Bundle), not an APK. The builder gives you the AAB free with every build, signed with a key that stays the same for the same package name, so keep that package name for every update and raise the version number each time. Before you submit, go through the Play Store checklist: a privacy policy, screenshots, the data-safety form and, for a new personal developer account, the closed test with testers.

If Play reports that the signing key does not match, read fixing the upload key error.

Questions

Is it free to convert a Lovable app to an APK?

Yes. The website builder is free and needs no account. The AppMint Android app is free to use as well; see pricing for what the paid plans add.

Do I have to rebuild the app every time I change it in Lovable?

Not if you wrap the published URL: the app loads the live site, so publishing in Lovable updates every installed app. You only rebuild to change the app name, icon, permissions or version for Google Play. A ZIP build does need a rebuild, because the code is inside the app.

Can I publish a Lovable app on Google Play?

Yes. The builder gives you the AAB file Play requires, free; upload it in Play Console. Google also expects the app to be more than a website in a frame, so use native features like push notifications, and keep the checklist in the Play Store checklist handy.

Does the Supabase login keep working?

Yes. The app stores the session the same way the browser does, so users stay signed in between launches.

Is "Loveable" the same thing?

People often spell it "Loveable". The product is Lovable (lovable.dev), and everything on this page applies to it.

Other builders

Last checked 2026-09-25.