Futurista Soft Book a call (opens in a new tab)
Founder guide

How to turn a Lovable app into an iOS and Android app

Last reviewed 21 November 2026

Lovable gets you a working web app, and customers start asking where the app is. There are three ways to get onto phones. One is quick, one is the usual middle road, and one is a proper rebuild. Here’s how to choose, and the problems that catch people out on the way to the stores.

Short answer

Lovable builds web apps, not native ones, and it doesn’t generate React Native code. You can make it installable as a PWA, wrap it with a tool such as Capacitor and submit it to the stores, or rebuild the key screens as a mobile app. Wrapping works best when you add real app features, because Apple rejects apps that are just a website, and Google sign-in won’t work inside an embedded web view.

What Lovable says

Lovable’s FAQ is clear: it doesn’t build native apps, and it doesn’t generate React Native projects. It builds web apps, which you can make mobile-friendly. To put one on phones, it points to two routes outside Lovable: a progressive web app (PWA), or wrapping your published app with a tool such as Capacitor and submitting it to the stores. A wrapper that only loads your live website is the kind Apple rejects as a website in a wrapper, so bundle the app’s files instead, as described below.

Three routes compared

RouteGood forWatch out for
PWA (installable web app)Testing demand quickly. People add it to their home screen from the browserNot in the App Store or Google Play, and fewer phone features
Wrap with CapacitorGetting your existing app into both stores, with access to push notifications, camera and other phone featuresApple’s Guideline 4.2 if it’s only your website in a shell, and sign-in inside the app
Rebuild as a mobile appApps people use every day, offline use, or heavy use of phone featuresA bigger job, though your Lovable app is still a working spec of what to build

Check how your app is built first

Lovable apps created before 13 May 2026 use React and Vite, which build into plain files that Capacitor can bundle into an app. Newer apps use TanStack Start, which runs code on a server. Capacitor needs a folder of built files with an index.html at its root. If your app was created on or after 13 May 2026, ask a developer whether it can be built as plain files. If it can’t, the parts that run on the server have to move to your backend before it can be wrapped. Get the code first: our export guide explains how.

Wrapping with Capacitor: what’s involved

This is developer work, but it helps to know the shape of it. Capacitor’s guide covers the detail.

Fixing login inside the app

Sign-in is where most wrapped Lovable apps break.

Getting through review

Phone features worth adding

Capacitor has official plugins for push notifications, camera, sharing, haptics and network status. Push notifications need Apple’s push capability on iOS and Firebase on Android. Pick features your customers will actually use: they help the app pass review, and they’re the reason to have an app at all.

Questions founders ask

Can I convert my Lovable app to an APK?

Yes, by wrapping it with a tool such as Capacitor and building it in Android Studio. An APK is fine for testing. Google Play needs an Android App Bundle instead.

Can Lovable publish straight to the App Store?

No. Lovable builds web apps. You wrap or rebuild the app outside Lovable, then submit it through your own Apple and Google developer accounts.

Do I need a Mac?

For the iPhone app, yes, or a developer who has one: building for iOS needs Xcode, which only runs on macOS. The Android app can be built on any computer.

Read next