LOVABLE → APP STORE + GOOGLE PLAY
Publish your Lovable app to the App Store and Google Play
Updated October 21, 2026
Lovable already ships a web app — here's the part that's missing
Lovable generates a production React app and deploys it to a yourproject.lovable.app address (or your custom domain). That's a fully working web product — but neither the App Store nor Google Play accepts a URL. Apple wants a signed .ipa, compiled on a Mac; Google wants a signed Android App Bundle, generated with a keystore you have to create and protect. That packaging-and-signing step is the gap between "my Lovable app is live" and "my app is in the stores." SaasToStore is the bridge: it builds, signs and prepares both apps for you, from the same URL you already have.
Looking for the Lovable manifest rather than the store? Lovable does not create one, and /manifest.json renders your app instead of a file — we measured what it really serves in the Lovable app manifest guide, with the fix.
From Lovable to both stores, step by step
- 01 ·
Publish your project in Lovable
In the Lovable editor, hit Publish (top-right). You'll get a public yourproject.lovable.app URL. If you connected a custom domain under Settings → Domains, use that — it makes the cleanest app identity and the strongest Digital Asset Links verification.
- 02 ·
Paste the URL into SaasToStore
We fetch your app name, icon, theme color and start screen. If your Lovable project doesn't expose a service worker, the Android build automatically switches to a Capacitor native shell, so the lack of one never blocks you.
- 03 ·
We build & sign your .ipa and your .aab
The iPhone app is compiled and signed on our macOS build machines. The Android bundle is signed with a unique RSA-2048 keystore — encrypted and kept for you, so future updates stay accepted by Google Play.
- 04 ·
Send them to the App Store and the Play Console
Send the iPhone build to TestFlight and App Store review from your dashboard, and upload the .aab to the Play Console with your listing (we can generate the icon, screenshots and description). Then the stores review your app.
Your Lovable app on the App Store: what Apple looks at
Google Play mostly checks that your app works. Apple also asks whether it is an app, and a few rules catch wrapped web apps more than any other. None of them depends on how the app was built — they depend on what your Lovable product does once it is on an iPhone.
On the build side, the iPhone app ships with what reviewers expect from an app: its own icon and launch screen, full screen with no browser bar, the native navigation you set up in the dashboard, and sign-in that comes back to the app. What it shows inside is your live Lovable product — so the review is about your product, and so is any fix: you change it in Lovable, publish, and the app picks it up.
Supabase sign-in, inside both apps
Most Lovable apps sign users in with Supabase. Email, password and magic-link logins work in the app as they are. Sign-in with Google needs one adjustment, because Google refuses to sign users in inside an app's web view — the error is disallowed_useragent, and it stops most wrapped apps on day one. Our builds open that sign-in outside the page — the system browser on Android, a secure sheet on iPhone — and bring the user back into your app, signed in. Your project gives you the return address to use and a prompt to paste into Lovable, so the AI makes the change for you; you then add the address to your Supabase redirect URLs.
Doing it yourself vs with SaasToStore
A typical Lovable launch
A solo founder finishes a habit-tracker in Lovable over a weekend — React front end, Supabase auth and database wired up, published to a custom domain. Monday morning they paste that domain into SaasToStore, set up a tab bar, and paste the sign-in prompt into Lovable. The Android bundle and the iPhone build come back the same day: the .aab goes to the Play Console, the iPhone build to TestFlight and then App Store review. Because the same URL also produced Windows and macOS installers, the product is on the desktop too. No Android or iOS knowledge was used at any point.
What you get for your Lovable app
- Signed iOS app (.ipa) for TestFlight and the App Store
- Signed Android App Bundle (.aab) + APK — the formats Google Play accepts
- Native header with a tab bar or side menu, shared by both apps
- Google sign-in that works in the app, with a ready-made Lovable prompt
- Capacitor fallback for Lovable projects without a service worker
- Encrypted keystore kept for you — updates never get rejected for a key mismatch
- Icon, splash and theme pulled straight from your app
- Optional AI-generated store icon, screenshots and description
- Same URL also builds Windows, macOS, Linux and Android TV apps
- One-time pricing: €39 for one app on every platform — no monthly lock-in
Building elsewhere too? See Bubble, Webflow, Framer and any website → APK. Want the iPhone side in more detail? Read how a website becomes an iOS app.
Frequently asked questions
Can I publish my Lovable app to the Apple App Store?+
Yes. The same Lovable URL that builds your Android app also builds a signed iOS .ipa for the App Store. iOS is included in SHIP (€39 one-time for one app on every platform). Apple then reviews the app like any other submission — see the next answers for what its review looks at.
Do I need a Mac, Xcode or an Apple Developer account?+
No Mac and no Xcode: the iOS build runs on our macOS build machines. To publish on the App Store, Apple requires an Apple Developer Program membership (99 USD/year), and your iOS build is signed with that account — so the app belongs to you, not to us. For Google Play you need a Play Console account (25 USD, once) to publish the signed .aab we deliver.
Will Apple accept a Lovable app?+
Apple judges every app on its own. The rule that matters is guideline 4.2 (minimum functionality): an app that only mirrors a website gets rejected, an app that feels like an app — its own navigation, a signed-in experience, no browser chrome — has a real chance. Two other rules catch wrapped web apps: digital goods sold inside the app must use Apple's in-app purchase (guideline 3.1.1), and if you offer Google sign-in you must also offer Sign in with Apple or an equivalent (guideline 4.8).
Does Google sign-in with Supabase work inside the app?+
Yes, after a three-step setup we show in your project: point the OAuth redirect to the app address we give you, allow that address in Supabase (Authentication → URL Configuration → Redirect URLs), and build. Google refuses to sign users in inside an app's web view, so the login opens in the system browser on Android and in a secure sheet on iPhone, then returns the user to your app, signed in. Email, password and magic-link logins need no setup.
Where do I find the URL to paste from Lovable?+
In the Lovable editor, click Publish (top right). Lovable deploys your project to a yourproject.lovable.app address — or to your own custom domain if you connected one under Settings → Domains. Copy that public HTTPS URL and paste it into SaasToStore.
Does my Lovable app need a PWA manifest or a service worker?+
Not for this. Lovable adds neither: of 56 published Lovable sites we ran through our own checker between June and September 2026, 36% had a manifest and only 5% had a service worker. A Trusted Web Activity — the lightest Google Play build — wants both, so we fall back to a Capacitor build that wraps any published HTTPS URL into a full native shell without either. The iOS build never needs them. If you do want to add a manifest, we wrote up exactly what Lovable serves and how to fix it.
Will my Lovable app be a real native app or just a webview?+
Both builds install and run like apps: their own icon, full screen, no browser bar, and a native header with a tab bar or side menu if you set one up. Inside, your Lovable app runs in a native web view, so what your users see is your live product.
My Lovable app uses Supabase auth and a database — will that keep working?+
Yes. The app loads your live Lovable deployment, so Supabase auth, your database, edge functions and any API calls behave exactly as they do in the browser. Nothing in your backend changes, and a change you publish in Lovable reaches the app without a new store submission.
What files do I receive at the end?+
For Google Play, a signed .aab (Android App Bundle) plus an APK for direct testing. For the App Store, a signed .ipa that you can send to TestFlight and App Store review from your dashboard, or upload yourself. We keep your Android keystore encrypted so future updates stay compatible.
How long does it take to get a Lovable app on both stores?+
The Android build takes about 5 minutes, the iOS build a little longer. After that, the wait is the stores' review: Apple usually answers within a day or two, Google Play's first review takes from a few hours to a few days. One exception: a personal Play Console account created after November 2023 must first run a closed test with 12 testers for 14 days before it can publish to production.
Can I also ship my Lovable app to desktop and Android TV?+
Yes. SHIP covers one app on every platform: the same Lovable URL also builds Windows (.msi), macOS (.dmg) and Linux (.AppImage) installers, and an Android TV app with remote-control navigation.
Ready to ship?
Paste your URL. We handle the build. You publish to the store.
Publish now