Lovable to iPhone app
Turn your Lovable app into a real iPhone app
Borel turns a Lovable app into a native iPhone app. Paste your app's address into Borel's chat: Borel opens it, photographs the first screen and reads its colours, logo and words, then writes the iPhone version in Swift and SwiftUI. You try it on a real iOS Simulator, install it on your phone and publish it to the App Store.
Updated
Native apps built by Borel, in the iOS Simulator.
Lovable
What does Lovable make?
Lovable builds web applications from a chat. You describe a product, it writes a React app, and one click publishes it to an address ending in lovable.app, or to a domain of your own.
Behind the pages sits Lovable Cloud, a backend built on Supabase. Your tables, sign-ins and uploaded files live there, which is why a Lovable app can feel finished so quickly in a browser.
The iPhone question
Why isn't a Lovable app an iPhone app already?
Lovable's publishing docs say it has no built-in flow that packages a project and submits it to the App Store. Your app lives at a web address, and on an iPhone it opens in Safari like any other page.
The usual workaround is Capacitor: the same React pages inside an app frame, built with Xcode on a Mac. That keeps the browser feel, scroll and all, and it's exactly the kind of app Apple's guideline 4.2 warns about. Lovable doesn't write React Native either, so there is no mobile codebase to start from.
Apple's rule
Why a rebuild beats a wrapper
Apple reviews every app before it reaches the App Store, and a website in an app's frame is what its guideline 4.2 is about.
“Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store.”
Borel never wraps your Lovable app. It writes a separate app in Swift with SwiftUI, Apple’s own language and interface framework, so the screens, scrolling and controls are the iPhone’s.
Step by step
How to turn your Lovable app into an iPhone app
- 1
Copy your Lovable address
Open your published project and copy its full address, starting with https://. Borel reads the public page, the one a signed-out visitor sees.
- 2
Paste it into Borel
Start a new app on borel.one with the prompt below. Screens behind your login? Attach screenshots of them, up to four per message.
- 3
Borel rebuilds it in SwiftUI
It reads your name, colours, logo and copy, photographs the first screen at iPhone and desktop size, and turns the React layout into tabs, lists and sheets.
- 4
Tap through it, then install it
The build opens in Apple's iOS Simulator, streamed to your browser for free. Borel Companion, on Pro, puts it on your own iPhone.
- 5
Ship it to the App Store
With Pro and an Apple Developer membership, Borel signs the build and uploads it to App Store Connect, all from the browser. Your Lovable site keeps running.
Your first message
A prompt to start from
Put your address where it says, fill in the brackets, and send it as your first message.
Make a native iPhone app of my Lovable app at <your address>. Keep its name, colours, logo and wording, and turn the web pages into iPhone screens with a tab bar. People sign in with email and save [what they save]. The main screens are [list them].
Moving over
What moves over, and what is made new
Borel works from what your app shows, the screenshots you add and the words you write. It doesn't copy code or accounts out of another platform.
| In your Lovable app | In the iPhone app |
|---|---|
| Look and brand | Moves over. Colours, logo, fonts and the feel of the first screen, read from the published app. |
| Pages and flows | Moves over. Rebuilt as iPhone screens from the page Borel opens and the screenshots you attach. |
| Words and content | Moves over. What the public page says, plus anything you paste in. |
| Lovable Cloud tables | Made new. The iPhone app declares its own tables in Borel's cloud. Rows don't copy across by themselves. |
| Signed-up users | Made new. People create an account in the iPhone app with email and password. |
| React code | Made new. Not imported: Borel writes Swift, which you can download. |
| The web app | Stays. Untouched, on lovable.app or your domain. |
Frequently asked questions
No. Lovable writes React for the browser, and an iPhone app in SwiftUI is built from different parts. Borel reads what your app shows, takes your look and screens from it, and writes the Swift version fresh.
They make a new account in the iPhone app, with email and password, in Borel's cloud. Sign-ins stored in Lovable Cloud stay there and don't move over.
It starts with its own database in Borel's cloud. If your data is reachable through an API that takes a key, save that key under Tools › Keys after the first build and ask Borel to read from it. The key stays on Borel's server, never in the app.
A wrapper shows the same web pages inside an app frame. It still scrolls and taps like a website, and Apple's guideline 4.2 asks for more than a repackaged site. A SwiftUI rebuild uses the iPhone's own navigation, lists and controls.
Yes. Borel sees the public page only, so attach screenshots of the screens inside, up to four per message, and say what each one does. Borel builds those screens from the pictures.
Paste your Lovable link
Watch the native version of your app open on a live iPhone in a few minutes.