Base44 to iPhone app

Turn your Base44 app into a real iPhone app

Borel turns a Base44 app into a native iPhone app, not a web view. Paste the address of your published Base44 app, and Borel looks at it, keeps its name, colours and logo, and writes the screens again in SwiftUI. The result runs on Apple's own controls, sells with in-app purchases if you want, and publishes to the App Store from your browser.

Updated

9:41
Idea Pipeline, a video idea tracker Borel built, on its Ideas tab
9:41
A recipe app Borel built, with recipes grouped by meal
9:41
A budget app Borel built, showing what is left to spend this month
9:41
A workout log Borel built, with this week's totals

Native apps built by Borel, in the iOS Simulator.

Base44

What does Base44 make?

Base44 is an AI website and app builder. You describe what you need, and it publishes a working web app at an address like myapp.base44.app, with pages, forms and dashboards that run in any browser.

Its data lives in entities, collections of records in Base44's own database, so the backend comes with the app rather than as a separate service you set up.

The iPhone question

Isn't Base44's App Store option already an iPhone app?

Base44 can package an app for the stores, and its docs are clear about what that package is: your published web app running inside a web view, a lightweight native wrapper. The files for submission need the Builder plan or higher.

A wrapper looks and scrolls like a website, because it is one, and Apple's guideline 4.2 asks apps to be more than a repackaged site. The same docs say Base44 apps can't use Apple's in-app purchases yet, which closes the usual way to charge on an iPhone.

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.”
App Store Review Guidelines, 4.2 Minimum Functionality, Apple

Borel never wraps your Base44 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 Base44 app into an iPhone app

  • 1

    Copy the base44.app address

    Take the published link from Base44, or your custom domain, and include https:// at the start.

  • 2

    Send it to Borel

    Paste the prompt below into a new chat on borel.one. For pages members only see after logging in, add screenshots: up to four per message.

  • 3

    A native rebuild, screen by screen

    Borel's Mac snaps your app's opening screen in phone and desktop sizes, reads its brand, and writes each screen with SwiftUI's lists, forms and tab bar.

  • 4

    Check it on an iPhone

    The iOS Simulator streams the real build to your browser, free on every plan. Borel Companion, on Pro, then installs it on your own phone to carry around.

  • 5

    Submit it for review

    On Pro, with Apple's Developer Program, Borel builds and signs the app on its Mac and hands it to App Store Connect in your account.

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.

Paste into Borel’s chat
Build a native iPhone app from my Base44 app at <your address>. Keep the name, colours and logo. Each entity becomes a list with a detail screen, and the dashboard becomes the first tab. Members sign in with email. Main screens: [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.

What moves from Base44 to the iPhone app
In your Base44 appIn the iPhone app
BrandingMoves over. Name, colours and logo from the base44.app page.
Pages and dashboardsMoves over. Rebuilt as native screens from what Borel sees and the pictures you add.
Labels and textMoves over. Read from the public page; paste in anything longer.
Entities and recordsMade new. The same shapes, declared again as tables in Borel's cloud. Existing records stay in Base44.
MembersMade new. They sign up again in the iPhone app with email and password.
PaymentsMade new. Digital sales move to Apple's in-app purchases, set up from Payments in Borel.
The base44.app web appStays. Keeps serving people on the web.

Frequently asked questions

Base44's store package runs your web app inside a web view. Borel writes a separate native app in SwiftUI, so scrolling, navigation and controls are the iPhone's own.

Yes. A Borel app can sell a subscription or a one-time unlock through Apple's in-app purchases. You set up the paid plan from Payments in Borel's menu.

Borel can build the same kinds of records as tables in its cloud database, from what you describe. The records already in Base44 stay there; nothing copies them across automatically.

No. The iPhone app has its own accounts in Borel's cloud, and members create one with email and password the first time they open it.

Only if you want to keep the web version. Borel never changes your Base44 app, so many people run the website and the iPhone app side by side.

Paste your Base44 link

Get a native iPhone version of your app to tap through in minutes.