Lovable Mobile Apps: PWA Installs, Store Wrappers and the Phone App

Can Lovable make a mobile app? Not a native one. Lovable builds web apps that run in any mobile browser, and it does not generate React Native projects or App Store and Google Play packages.^[1] Two routes still reach a phone's home screen. The first stays inside Lovable: ask the agent to turn the app into a progressive web app (PWA) that installs from Safari or Chrome. The second sits outside it: wrap the published URL with Capacitor and submit that wrapper through your own developer accounts. The Lovable mobile app is something else. It lets you keep building from your phone, and it does not publish what you build. If a store listing is the whole point, budget for the wrapper work or pick a builder with store output.

What a Lovable project looks like on a phone

Every Lovable project is a web app written in React, TypeScript and Tailwind. New projects since May 2026 (June 2026 on Enterprise) run on TanStack Start, which renders each page on the server, so a phone receives complete HTML on the first load. Lovable's FAQ says you can design an app to be fully mobile friendly, and the published result opens in any phone browser at its lovable.app address or on a custom domain. There is no iOS or Android build target. You also cannot switch to React Native or another framework, because Lovable fixes the stack for every project.

That choice shapes what the app can touch on a device. Lovable's docs explain that its apps run in the browser with a serverless backend, so Capacitor or Electron native plugin packages install without complaint but do nothing in the published app.^[2] Lovable's own comparison page against FlutterFlow spells out the consequence: no iOS or Android binaries, no store submission, no push notification frameworks and no camera APIs. Plan features around what a mobile browser allows. Booking pages, client portals, field forms and internal dashboards fit that model comfortably. An app whose core feature depends on native device access does not.

Turning the app into an installable PWA

The route Lovable itself points to is a progressive web app. You ask the agent in the project chat to make the app installable, and from then on it opens full screen from a home-screen icon instead of a browser tab. Lovable's Android page says users open the app in Chrome and tap Install app;^[3] its iPhone page says the app runs in Safari and can be added to the home screen.^[4] The request is an ordinary Build message, billed on the work done like any other edit. Nothing reaches users until you publish again.

1. Publish the app once, so there is a live address to install from. Publishing is free on every plan, publicly or invite-only for up to 10 people per project on Free and Pro.
2. In Build mode, ask Lovable to make the app a progressive web app (PWA) that can be installed on Android and iPhone.
3. Open the Publish dialog and choose Publish changes, because the live site is a snapshot of the last publish.
4. On an Android phone, open the address in Chrome and tap Install app. On an iPhone, open it in Safari and add it to the home screen.
5. Check the installed copy on both platforms before you send the link to real users.

One upgrade trap deserves a line. When an older React + Vite project moves to TanStack Start, Lovable warns that PWA installs may keep a saved copy of the old version, so check installed phones after you publish the upgrade. Free apps created since May 2026 are also limited to 1,000 server requests per project per 10 seconds, while paid plans put no cap on visitors or bandwidth. The Lovable badge stays on Free apps; hiding it starts on Pro.

Store listings mean a Capacitor wrapper you build yourself

For an App Store or Google Play listing, Lovable's FAQ names one path: wrap the published URL with Capacitor, outside Lovable. Nothing in the editor does this step. You take the live address, build the wrapper in your own tooling, sign it and submit it under your own developer accounts, paying whatever Apple and Google charge. Lovable support will not carry that work, since its policy excludes debugging project code and implementing third-party integrations. Apple's review then decides. Replit's documentation, covering the same Apple step for its own users, notes that Apple requires a developer account with an annual membership fee before anything can be uploaded, even for private testers.

Because the wrapper loads your live site, three Lovable rules follow it into the store. First, lovable.app subdomains belong to Lovable and can be reclaimed, generally with seven days' notice, and Lovable advises a custom domain for mission-critical apps. Custom domains need a paid plan. Pro with 100 credits is $25 per month billed monthly or $21 per month billed annually, per workspace. Second, every person who opens the wrapper spends your workspace credits on the backend and AI features, exactly as browser visitors do. Third, at zero credits the built-in backend pauses until you add credits and click Wake up; our pricing guide covers the credit rules.

Keeping the wrapper next to the web code is possible, with limits. Git sync exports a project on any plan to a new private repository on GitHub, GitLab or Bitbucket Cloud, two-way, one branch at a time. It cannot connect an existing repository, so a wrapper project you started elsewhere stays in its own repo. Pushing to the synced repository never publishes the app. Database records, stored files and secrets do not travel with the code either.

The Lovable phone app builds, it does not publish

Lovable launched its own mobile app for iOS and Android in April 2026, and the name misleads. It is a way to use Lovable, not a way to ship your project. It runs on iOS 15 or later (iPhone and iPad) and Android 9 or later, and it shares the same account, projects and credits as the web editor. You can dictate prompts, attach a photo from the camera, sign in with Google or Apple, work in drafts, and opt in to push notifications that say when a build is ready or needs your input.

Some work still waits for a desk. Detailed code review, the preview toolbar and inline comments on the preview remain desktop-only, according to Lovable. Billing differs too. A plan bought inside the iOS app goes through the App Store, covers one month and does not renew, and Apple handles its receipts and refunds. The mobile app has no cancel option, so canceling from a phone means opening Lovable in a browser. Messages sent from the phone are billed like any other Build message, failed attempts included, from the same workspace balance.

Replit and Base44 take other roads to the stores

If a native app is the requirement, Replit is the sharpest contrast. Its Agent builds native iOS apps with Expo: you test on a real phone by scanning a QR code into Expo Go, then Replit builds the app in the cloud and submits it to App Store Connect for TestFlight review. Publishing to Google Play is not supported yet. You still need an account enrolled in the Apple Developer Program, the bundle ID cannot change after the first build, and Apple's review often takes a day or two. Billing is effort-based rather than per message; our Lovable vs Replit comparison sets the two side by side.

Base44 sits between them. Its apps are web apps too, but on its Builder plan and higher it generates store-ready wrapper files (IPA for iOS, AAB for Google Play) that run the published app inside a web view, plus push notifications. Base44 signs those files, and you submit them through your own Apple and Google accounts. Base44 Builder is $50 per month billed monthly or $40 per month billed annually. A Base44 credit and a Lovable credit measure different units, so compare only plan prices on the same billing term; the Base44 vs Lovable breakdown does exactly that.

Matching the route to what you are building

Internal tools, client portals and early MVPs are where the PWA route holds up. Users install from a link, you skip store review, and every publish reaches them at once. Free covers a first version with 5 build credits a day, up to 30 a month, and public or invite-only publishing. A team that wants its own domain and no Lovable badge moves to Pro. None of this needs an Apple or Google account, which keeps the launch inside one tool and one bill.

A consumer product that must be found in a store is a different calculation. Count the wrapper build, both developer accounts, store review rounds and a paid Lovable plan for the custom domain, then compare that with a builder that produces store files itself. An app built around native device features is the clearest mismatch: native plugin packages do not work in a Lovable app, so for anything beyond what a mobile browser allows, starting elsewhere saves a rebuild later.

The bottom line

Lovable answers the mobile question honestly: it ships web apps, and phones get them through the browser or a PWA install. That is enough for internal tools, portals and MVPs; beyond the build credits its edits use, the app's running cost is the Cloud and AI usage that visitors draw from the same workspace credit balance. Store presence is possible only through a Capacitor wrapper you build, sign and maintain yourself, against your live URL and your credit balance. If the App Store is the product, Replit's native Expo path or Base44's wrapper files deserve a look before you commit.