The short answer. In the Base44 editor, scan your app against the store guidelines (free), fix what the scan flags with Base44’s AI, then generate the iPhone file (IPA) and the Android file (AAB). Downloading those files needs the Builder plan or higher. You then submit them yourself from your own Apple and Google developer accounts. In Base44’s words: “You still need to submit the app through your own App Store Connect and Google Play Console accounts.” Budget for Apple’s 99 USD a year, Google’s US$25 once, and, on a new personal Google account, a 14-day closed test with 12 testers before you can publish.
What Base44 builds for the stores
Base44’s mobile app is a native shell around your live web app. The docs describe it as “a lightweight native wrapper around your web app that opens only your app's URL” and say “Your mobile app runs your published Base44 app inside a secure web view.”
Two things follow from that. First, “most changes reach your mobile app as soon as you publish them in Base44”, so you do not resubmit for every update. You need new store files only when the app’s name, icon, splash screen, push notifications or permissions change. Second, the app can do what your web app can do, plus what the shell adds, such as push notifications. Features that need native code are not available (see the limits below).
Base44 added store publishing in early 2026; tech.co reported it on 9 February 2026 as “Base44 Users Can Finally Publish Creations to App Store”.
Before you start: what you need
A Base44 plan that can download the files. The scan runs on the Free plan. Base44’s docs: “to download the files for app submission you must be on the Builder plan or higher”. Builder is $40 a month billed annually on Base44’s pricing page.
An Apple Developer account. 99 USD a year. Enrolling as an organisation needs a D-U-N-S number, which can take several business days to get, so start this first.
A Google Play developer account. US$25 once. If it is a new personal account, Google requires a closed test with at least 12 testers for 14 days before you can apply for production access. Plan the testers before you generate the Android file.
Store listing material. App name, description, screenshots for each device size, an app icon, a privacy policy URL and, for Apple, the App Privacy answers about what data the app collects.
Base44 is explicit about who pays: “You are responsible for setting up and paying for your Apple and Google developer accounts.”
Step 1: Create your developer accounts
Enrol in the Apple Developer Program and register a Google Play Console account. Use the legal name you want shown in the stores. If you enrol as a company, Apple and Google both verify the organisation, which adds days.
Step 2: Scan your app for issues
In the Base44 editor, run the store readiness scan. It checks the app against the App Store and Google Play guidelines and gives a readiness score with a list of issues. The scan is available on the Free plan, so you can run it before you pay for anything.
Step 3: Use AI to fix issues
Send the flagged issues to Base44’s AI chat to fix them, then scan again. Base44: “You do not need a readiness score of 100 before you submit.” It also says “Base44 cannot guarantee that an app is approved, even with a high readiness score.”
Step 4: Generate your app files
Generate the IPA (for the App Store) and the AAB (for Google Play). Push notifications are turned on here: “You turn them on in the same window where you generate your store files.” Decide on push before you generate, because changing it later means new files and a new store submission.
This is the step that needs the Builder plan or higher.
Step 5: Submit to the App Store
In App Store Connect, create the app record, upload the IPA, fill in the listing, the App Privacy answers and the age rating, and submit for review. Base44’s troubleshooting notes refer to Apple’s Transporter app for uploads; Transporter runs on a Mac. If you upload a build to TestFlight first, you can try the app on your own iPhone before review.
Apple says 50% of submissions are reviewed in under 24 hours and 90% in under 48 hours. The rule that matters most for a web view app is guideline 4.2: “Your app should include features, content, and UI that elevate it beyond a repackaged website.” Push notifications, a phone-first layout and screens that work without the browser help. How to publish an app on the App Store covers each App Store Connect screen.
Step 5: Submit to Google Play
In Google Play Console, create the app, complete the app content forms (privacy policy, data safety, content rating, target audience), and upload the AAB.
On a new personal account, upload it to a closed testing track first, invite at least 12 testers and keep the test running for 14 days. Then apply for production access; Google’s review of that application usually takes up to 7 days. After that, release to production. The rule applies to personal accounts; organisation accounts are not subject to it.
After launch, Base44’s docs say “You are responsible for checking your submission status, responding to store emails”, which includes rejections and policy notices.
What the Base44 mobile app cannot do (yet)
From Base44’s documentation, read 29 October 2026:
No in-app purchases. “Base44 apps don't support Apple In-App Purchase or Google Play Billing yet.” And: “Apple and Google reject apps that sell digital content through any payment provider, including Stripe.” If you sell subscriptions or digital goods, the store version cannot sell them today.
No mobile ads. “Base44 mobile apps don't support AdMob or other mobile ad networks.”
No offline mode or HealthKit. “Full offline mode and HealthKit are not supported yet.”
No native-only features. Face ID and fingerprint sign-in, background location and passkeys need native code the Base44 shell does not include.
Fixed settings. The app stays in portrait mode; “You can't choose or change your bundle ID or package name”; permissions are not editable in the Base44 interface.
If your app depends on one of these, the Base44 store version will not cover it, and one of the routes below will.
Other ways to get a Base44 app into the stores
A converter service. Median, Despia and Natively wrap your published Base44 URL in their own native shell and add native plugins; Median and Despia list in-app purchases among them. Median: “Median turns your Base44 URL into a native iOS and Android app without asking you to rebuild the product in Swift or Kotlin.” They are still web view apps. Website to app converters compared lists prices.
Export the code and wrap it yourself. On the Builder plan or higher, Base44 exports your code to GitHub or as a ZIP, and its docs name Capacitor, PWABuilder and Trusted Web Activity as wrappers. Base44: “These wrappers are managed outside of Base44, and any native-only features like push notifications must be set up separately.” You need a Mac with Xcode for the iPhone build. What is Capacitor explains that route.
Rebuild it as a native app. Use the Base44 app as the reference and build the phone app in Swift for iPhone and Kotlin for Android. This is the route for apps that need in-app purchases, offline use, Face ID, widgets or background work. Modaal is built for it: you describe the app, Modaal turns it into a requirements document and a spec per feature, and your own AI agent builds a native SwiftUI app and a native Jetpack Compose app from the same project. It runs on a Mac. The Free plan covers one project on one platform; Pro (€9 per user per month billed annually) adds both platforms, TestFlight and automated App Store publishing.
The routes side by side
| Route | What the store gets | Who submits | In-app purchases | What you pay besides store fees |
|---|---|---|---|---|
| Base44 mobile app | Native shell, your app in a web view | You, from your own accounts | Not yet | Base44 Builder plan or higher to download files |
| Converter (Median, Despia, Natively) | The converter’s native shell, your app in a web view | You, or the vendor on some plans | Through the vendor’s plugins | The converter’s plan |
| Export + Capacitor | Capacitor shell, your exported code in a web view | You | With a plugin you add | Base44 Builder plan to export; a Mac with Xcode |
| Native rebuild | A Swift app and a Kotlin app | You, or the tool on some plans | Yes, with StoreKit and Play Billing | The tool or developer; a Mac for iPhone |
From Base44’s documentation and the vendors’ own pages, read 29 October 2026. Store fees: Apple 99 USD a year, Google Play US$25 once.
Keep reading
- Can Base44 make mobile apps?
What the web view app can and cannot do.
- Website to app converters compared
Median, Despia, Natively and five more, with prices.
- How to publish an app on the App Store
Every App Store Connect step.
- What is Capacitor?
The wrapper Base44’s docs name for exported code.
Native iPhone and Android apps. Start free.
One project, two native apps: Swift for iPhone, Kotlin for Android.
