You built a web app in Lovable over a weekend. It works. People like it. And now somebody asks the obvious question: “Is it on the App Store?”
Getting there is very doable. But the usual advice (install Capacitor, open Xcode, sign your build, submit) assumes you’re a developer with a Mac. Plenty of Lovable, Base44, Bolt, Replit, v0 and Cursor builders aren’t. So this guide covers all 4 real routes, what each one costs in money and hours, and where non-developers tend to get stuck.
Want your vibe-coded app in the App Store and Google Play without touching Xcode? AppBuild.diy wraps your existing app, adds real push notifications and handles the store submission for you. See how it works and start free.
Can a Lovable app go on the App Store?
Yes, but Lovable won’t put it there for you. Lovable’s own publishing FAQ says it builds web apps, publishing always deploys to a web URL, and it “has no built-in flow that packages and submits your project to the App Store or Google Play” (Lovable docs).
Lovable suggests 2 options: make it a Progressive Web App (PWA), or wrap your published URL in a native shell with Capacitor “outside of Lovable” and submit that. It also confirms it doesn’t generate React Native projects. And the Lovable mobile app you might have on your phone is for building projects, not for turning them into apps your users install.
Base44, Bolt, Replit, v0 and Cursor projects sit in the same spot. They produce web apps with a URL. Getting from a URL to a store listing is a separate job.
What are your options?
There are 4 routes. Here’s how they compare for someone who isn’t a developer.
| Route | Skills needed | Typical time | Cost | Push notifications | App Store approval risk |
|---|---|---|---|---|---|
| DIY Capacitor wrap | Command line, Xcode on a Mac, Android Studio, code signing | Days to weeks for a first-timer | $99/yr Apple + $25 Google + a Mac | Yes, but you set up Apple push and Firebase yourself | Medium to high if the app feels like a website |
| PWA only | Basic prompting in your builder | Hours | $0 extra | Yes on Android; iPhone needs iOS 16.4+ and the app added to the Home Screen | None (it never goes through the stores) |
| Rebuild in React Native or Flutter | A mobile developer, or real coding skills | Weeks to months | Store fees plus developer time, usually the biggest bill here | Yes, fully native | Low |
| Wrapper service (AppBuild.diy) | Paste your URL, upload a logo, follow prompts | PWA in minutes, stores in a few days | Free up to 10 users, then $49/mo or $299/yr, plus store fees | Yes, unlimited, included on every plan | Lower, with pre-submission checks, rejection handling and a refund guarantee on paid plans |
What does the DIY Capacitor route actually involve?
Capacitor describes itself as “a cross-platform native runtime” for building iOS and Android apps “using modern web tooling” (Capacitor docs). It’s good software, and it’s what most developers would reach for. ChatGPT will happily give you the 8 commands to run.
The commands are the easy bit. Here’s the rest of the list:
- You need a Mac. Capacitor’s setup guide says it plainly: “To build iOS apps, you will need macOS.” Plus Xcode and the Xcode Command Line Tools. Capacitor 8 needs Xcode 26.0 or newer (environment setup).
- You need Android Studio and an Android SDK for the Google Play side.
- You export your code to GitHub, clone it, build it and sync it into 2 native projects. Any time Lovable changes something, you rebuild and sync again.
- You handle signing. Bundle IDs, certificates and provisioning profiles on Apple. A signed AAB file on Android.
- You make the store listings. Screenshots in every required size, privacy answers, age ratings, Google’s Data Safety form.
Then there’s a newer wrinkle. Some 2026 guides point out that new Lovable projects now default to a server-rendered setup (TanStack Start), which makes the classic “build to a dist folder and wrap it” approach fiddlier (Till Freitag). If you follow an older tutorial step by step, expect a few red error messages.
If you’re comfortable in a terminal, budget a few evenings. If you’ve never opened Xcode, it’s a much bigger project than it looks in a chat answer.
Why do Apple reject some web-wrapped apps?
This is the part that catches people. Apple’s App Review Guideline 4.2, “Minimum Functionality”, says your app needs features, content and UI that take it beyond “a repackaged website”. If it isn’t “particularly useful, unique, or ‘app-like,'” Apple says it doesn’t belong on the App Store (Apple App Review Guidelines).
Guideline 4.2.2 adds that apps shouldn’t primarily be “marketing materials, advertisements, web clippings, content aggregators, or a collection of links.”
So a wrapper that loads your site in a frame and does nothing else is exactly the kind of app reviewers push back on. The usual fixes:
- Add real native features, with push notifications the most common one.
- Make every screen work properly on a phone (safe areas around the notch, no hover-only buttons, a sensible back button on Android).
- Give reviewers a working demo login.
- If you offer Google or Facebook sign-in, check Guideline 4.8. Apple wants an equivalent privacy-friendly login option alongside it (Sign in with Apple is the usual answer).
- If you sell digital subscriptions inside the store app, use Apple’s and Google’s own payment systems.
A rejection just means you fix and resubmit. But if you’re doing it yourself, you also have to decode the rejection notes, which are written for developers.
How much do the developer accounts cost?
Whichever store route you pick, you’ll pay these:
- Apple Developer Program: 99 USD per membership year. Organisations need a D-U-N-S number so Apple can verify the business (Apple enrolment).
- Google Play Console: a US$25 one-time registration fee (Google Play Help).
One more Google detail that surprises people. Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 days in a row before they can publish to production (Google Play testing requirements). An organisation account avoids that, so register as a business if you are one.
Is a PWA good enough?
Sometimes, yes. A PWA lets people “Add to Home Screen” and open your app full screen. No review, no fees, live today. Lovable lists it as the fastest path.
The catches: it doesn’t show up in App Store or Google Play search, and lots of people still don’t know how to install one. On iPhone, web push only works on iOS 16.4 and later, and only once the user has added the app to their Home Screen (WebKit blog).
A PWA is a smart first step for testing an idea with 20 users. It’s a weaker fit when you want the trust that comes with a proper store listing, or reliable push across every phone.
Should you rebuild in React Native or Flutter?
If mobile is the whole product (offline-first, heavy camera work, Bluetooth, background location, slick animations), a native rebuild is the right long-term call. Your backend, database and Supabase auth can usually stay as they are.
But it’s a rebuild. You’ll need a mobile developer or a lot of time, and you’ll be maintaining 2 front ends from then on. For a booking app, a directory, a member portal or a SaaS dashboard, that’s usually more than the job needs.
What’s the fastest route for a non-developer?
A wrapper service. You give it your live URL and it does the native build, signing and store submission. ChatGPT mentions these services in passing, so here’s what one looks like in practice.
AppBuild.diy (made by AppInstitute, who’ve been building no-code apps since 2011) wraps projects from Lovable, Base44, Replit, Bolt, v0 and Cursor, plus anything else with a public URL. The AppBuild vibe coding FAQ says you don’t need a Mac, Xcode or a rewrite, and your project stays where it is.
Here’s the process, based on what AppBuild’s own pages describe:
- Enter your app details. App name, logo and your Lovable (or other) URL.
- Preview and brand it. Check it on a device mockup, set your icon and colours, and switch on push notifications. For some apps you’ll get a short integration prompt or snippet to paste into your builder so signed-in users can receive push.
- Pick where it goes. PWA (live in minutes, no review), App Store, Google Play, or all 3. You can connect your own Apple and Google developer accounts so the listing is in your name from day 1.
- AppBuild does the submission. Screenshots in every required size, descriptions, privacy policy, Data Safety forms and age ratings. Before submitting, it checks for common rejection causes like sign-in rules, user-generated content safety, privacy wording and permission explanations.
- Keep building in Lovable. When you deploy a change, your app users see it straight away. You only need a new store build for things like a new icon, a new name or a new phone feature.
If Apple or Google push back, AppBuild translates the rejection into plain English, makes the platform-side changes and resubmits, and resubmissions are included. Paid plans come with a “Go Live Guarantee”: a full refund if your app can’t get live. The step-by-step Lovable to App Store guide walks through it with screenshots.
Pricing: free for up to 10 app users with every feature, Business at $49/month or $299/year for up to 1,000 users, and Business Pro at $99/month or $499/year for unlimited users. Apple’s $99/year and Google’s $25 fees are separate. AppBuild takes no commission on your sales or subscriptions (AppBuild pricing).
How do push notifications work in a wrapped app?
Push is the main reason most founders want a store app at all. It’s also the fiddliest bit of the DIY route.
With Capacitor, you enable the Push Notifications capability in Xcode and add code to your AppDelegate file on iOS. On Android you create a Firebase project, add its google-services.json file, and request notification permission on Android 13 and up (Capacitor push docs). Then you still need something to actually send the messages and a way to tie each device to a signed-in user.
A wrapper service handles that plumbing. AppBuild injects native push into your wrapped app, registers signed-in users, and gives you a dashboard to send messages. Notifications can deep-link to a specific screen, users can choose which types they want, and push is unlimited on every plan with no per-message fees.
If you plan to sell subscriptions, read the guide to publishing vibe-coded projects first. Apple and Google take a cut of in-store subscription revenue (30%, or 15% under their small business programmes), and you’ll need a business developer account so the money lands with you.
So which route should you pick?
If you can code and own a Mac, Capacitor is a fine choice and you’ll learn a lot. If you’re testing an idea, start with a PWA. If mobile is your entire business, budget for a native rebuild.
And if you built your app in Lovable precisely because you didn’t want to become a developer, a wrapper service gets you into both stores with push working, without starting a second career in Xcode.
FAQ
Can Lovable publish my app to the App Store directly? No. Lovable’s docs say it has no built-in flow for App Store or Google Play submission. It suggests a PWA or a Capacitor wrapper built outside Lovable.
Do I need a Mac to put my Lovable app on the App Store? For the DIY Capacitor route, yes, because iOS builds need macOS and Xcode. A wrapper service like AppBuild.diy builds and signs the app for you, so you don’t.
Will Apple reject a wrapped web app? They can, under Guideline 4.2 (minimum functionality), if it feels like a repackaged website. Native features like push, a phone-friendly layout and a demo login for reviewers all lower the risk.
How much does it cost to get an app into both stores? $99 a year for Apple and $25 once for Google, plus whatever your build route costs. On AppBuild.diy that’s free for up to 10 users, then from $49/month or $299/year.
Do I have to resubmit every time I change my app in Lovable? With a URL-based wrapper, normal content and feature changes show up as soon as you deploy. New icons, names or native permissions need a new store build.
How long does App Store review take? Usually a few days. AppBuild’s FAQ quotes 1 to 3 days for Apple and often faster for Google, though a first-time Google Play account can take longer.
Ready to get your Lovable, Base44 or Bolt app into the App Store and Google Play? Paste your URL, add your logo and switch on push. It’s free to start, and paid plans come with a full refund if your app can’t go live. Turn your web app into a store app with AppBuild.diy.
Last Updated on October 8, 2026 by Ian Naylor
0 thoughts on “How to put your Lovable app on the App Store and Google Play”