How to convert a Base44 app to iOS and Android
Base44 can package a published app for the Apple App Store and Google Play. The Base44 built-in flow is a good choice when you need a store listing and a basic app without any native-only features. Median.co is a better fit when you need push notifications, native features, more control over the app shell, or help managing app store submissions. However you convert your Base44 app to a mobile app, you should test login, payments, file and photo uploads, permissions, and real-device behavior before launching.
You can convert a Base44 app to iOS and Android without rebuilding it in Swift or Kotlin. If the app already works well on a phone, you have two practical options. Base44 can generate store-ready files from the published app, or you can use Median.co to wrap the same live app as an iOS and Android app with a much deeper set of native features.
Which one is right depends on what the mobile app has to do after it opens. This guide compares the two and shows what to test before you submit.
Build a mobile app from your Base44 URL
Can Base44 make mobile apps?
Yes. Base44's official app store flow scans a published app, suggests mobile fixes, and packages it for iOS and Android. You get an iOS file for App Store Connect and an Android App Bundle for Google Play, and you submit both through your own Apple and Google developer accounts.
The resulting app is a wrapper around your live Base44 app, which matters for two reasons. Most content and design changes published in Base44 appear in the mobile app without another store release. Changes to the native shell, such as the icon, splash screen, permissions, or native integrations, still require a new build and usually a store update.
Base44 says its current wrapper doesn't support native-only push notifications, full offline operation, or integrations such as HealthKit. If any of those are core requirements, settle the mobile approach before you create store records and bundle IDs.
Base44's built-in upload or Median.co?
Choose Base44's built-in app store upload when:
Your published Base44 app is already mobile-ready.
A store listing is the main goal.
You do not need push notifications or a broader native plugin library.
You are comfortable managing App Store Connect and Play Console yourself.
Choose Median.co when:
You need push notifications, biometrics, haptics, deep links, native navigation, or vendor SDKs.
You need more control over link handling, permissions, loading states, and the native app shell.
You want one configuration for iOS and Android.
You want Median.co's team to manage store submission and review follow-up.
Neither option turns the Base44 interface into a fully native Swift or Kotlin interface. Both are web to app conversions rather than rewrites, which works in your favor while the Base44 project is still changing, because there's no second mobile front end to keep in sync.
Get the Base44 app ready for a mobile wrapper
Start with the public production URL, not an editor preview, and open it on a small iPhone and an Android phone before creating a build.
The parts that expose the difference between a desktop browser and an installed app are always the same:
Navigation: Every screen should be reachable without hover menus or desktop-only controls, and Android's back button should not close the app unexpectedly.
Login: Test email links, password resets, Google or Apple sign-in, and redirects back into the app. A login that works in Safari can still fail inside a wrapper if redirect domains are incomplete.
Uploads and permissions: Test the camera, photo library, microphone, file picker, location, and downloads on a physical device.
Loading and errors: Give users a useful loading screen and a clear offline message. A blank screen during a slow Base44 startup looks like a crash.
Account controls: If users can create accounts, both stores expect a way to delete an account. Make support and privacy links easy to find.
Payments: Separate payments for physical goods or real-world services from digital subscriptions and features. Digital purchases may need Apple In-App Purchase and Google Play Billing.
You don't need a code export for either of these wrappers. The published HTTPS URL is enough, and exporting only matters when you plan to take over the codebase or build a separate native client.
How to convert a Base44 app to iOS and Android with Median.co
Median.co's website to app setup runs entirely from the published URL, so Base44 stays your editor and host throughout.
1. Publish the Base44 app
Publish the project and copy its public URL. A Base44 subdomain is fine, and you don't need a custom domain just to create the mobile app.
2. Create the app in the Median App Studio
Open the Median App Studio, enter the Base44 URL, and set the app name. Median.co builds an iOS and Android configuration around the hosted app.
The Base44 setup guide covers the optional Median JavaScript Bridge, which you'll want when the web app needs to call native functions such as haptics or read push notification data. If Base44 installs the npm bridge in your project, enable the matching JavaScript framework setting in the Median App Studio so the bridge isn't injected twice.
3. Configure the app shell
Add the app icon, splash screen, theme colors, link rules, and permissions, and only request device permissions a user can connect to a visible feature.
This is also where native capabilities come in. A Base44 app can register for Median.co push notifications and pass the device identifier to your backend, and the web app then decides which user should receive each message.
4. Test on actual iOS and Android devices
The browser preview is useful for layout and nothing more. It can't prove that OAuth, notifications, purchases, camera access, or keyboard behavior will survive an installed build, so test every account flow and permission on at least one real iPhone and one real Android device.
5. Build and publish
Create the signed release builds once the configuration is stable. Median.co can hand the build files to your team to submit, or the Publishing Service can manage the submissions and respond to review questions.
Base44 to APK versus Google Play
An APK is for direct Android installation and testing, and that's the extent of it. Google Play expects an Android App Bundle for a new release, usually called an AAB, and generates device-specific APKs from it.
Use an APK to find out whether the Base44 app behaves correctly when installed on a phone. Use the AAB and Play Console when the goal is a signed, documented, reviewed app that the public can install and update. The Apple side of a Base44 to app store launch has no APK equivalent at all, since iOS builds are signed and delivered through App Store Connect.
Don't make an APK downloader the main launch plan if customers expect to find the app in Google Play. Direct downloads create trust, update, and device-security friction that a store release avoids.
How to publish a Base44 app to the Apple App Store
You need an Apple Developer account, an App Store Connect record, a stable bundle ID, screenshots, support and privacy URLs, and accurate privacy disclosures.
Before submission:
Upload the signed iOS build and test it through TestFlight.
Give App Review a working demo account if login is required.
Explain any native features and where the reviewer can find them.
Confirm that account deletion and subscription management are available when required.
Make sure the app offers more than a thin view of public website content.
If a Base44 app is already in App Store Connect, keep its existing bundle ID when moving to a new build provider. Changing the bundle ID creates a different app instead of updating the one customers already installed.
How to publish a Base44 app to Google Play
Create the app in Play Console with the same package name the Android build uses, then complete the store listing, Data safety form, content declarations, privacy policy, app access instructions, and the required testing track.
Upload the signed AAB to an internal test first and run login, billing, notifications, uploads, and links from that installed Play build. When the release is ready, promote it to production and keep the signing keys and package name unchanged for every future update.
Push notifications, offline access, and subscriptions
Decide these three early, because they shape both the architecture and the store review.
Can a Base44 app send push notifications?
Base44's built-in wrapper currently lists native-only push notifications as unsupported. Median.co adds native push registration and delivery while Base44 remains the web interface. You still need a way to associate each device with the correct Base44 user and to trigger messages from your backend or notification provider.
Will a Base44 app work offline?
A wrapper can't make a server-backed Base44 app fully offline on its own. You can add a friendly offline screen and cache selected assets, but anything that needs Base44's backend still needs a connection. If field work without connectivity is a core use case, define exactly which records, photos, and actions must sync later before choosing a wrapper.
Can I keep Stripe in a Base44 mobile app?
Stripe stays appropriate for physical goods and real-world services. Digital subscriptions, content, credits, or features sold inside the app may need Apple and Google billing instead. Median.co supports RevenueCat as a shared subscription layer across both stores, and it's work to plan before review rather than after a payment-policy rejection.
Frequently asked questions
How do I convert a Base44 app to a mobile app?
Publish the Base44 project, make the layout work on phone screens, and choose either Base44's built-in store packaging or a platform such as Median.co. Base44 is the shorter road to a basic store wrapper. Median.co fits when the app needs native plugins, push notifications, app-shell control, or managed publishing.
Can Base44 publish to the App Store?
Base44 can generate the iOS file and guide you through its mobile scan, but you still need your own Apple Developer account and App Store Connect submission, and Apple reviews the finished app under its normal guidelines.
Can Base44 publish to Google Play?
Yes. Base44 can generate an Android App Bundle for upload to Play Console. The developer account, store listing, declarations, testing requirements, and production rollout stay your responsibility.
Does Base44 have an iOS app?
Base44 runs in the browser, and a published Base44 project is a web app. To get yours on the App Store as an iOS app, use Base44's built-in store packaging or build the wrapper app with Median.co, then submit it through App Store Connect.
Does my Base44 app update without a new store submission?
Mostly. Changes to the hosted Base44 pages appear when the installed wrapper reloads the live app. Native-shell changes such as the icon, permissions, plugins, or signing configuration need a new build and usually a store update.
Can I turn Base44 into an iOS app without Xcode?
Yes. Base44 can generate its iOS store file, and Median.co builds signed iOS apps in the cloud. You still need Apple credentials, App Store Connect setup, device testing, and review materials.
Do I need a Base44 code export?
Not for a URL-based mobile wrapper, which only needs the published HTTPS URL. Export the code when you want to maintain the generated source yourself or build a separate native application.
How do I download my Base44 app?
Downloader extensions and export tools pull your source code out of Base44, which is useful when you plan to host or maintain the code yourself. If the goal is your app on a phone, there's nothing to download. You build an installable app from the published URL. A Base44 mod APK from a download site is someone else's build, not yours, so don't install it.
Can I move an existing Base44 app to Median.co?
Yes. Keep the existing bundle ID, Android package name, signing ownership, and store records, and test the replacement build as an update before it goes to production. That preserves the listing and lets existing users receive the new version as a normal update.
Choose the route around the product, not the file format
Base44's own store flow now covers the basic conversion many projects need, so start there if the app is mobile-ready and the current feature limits don't bite.
Use Median.co when the installed app has to do more than display the Base44 experience, or when your team wants help with signing, store configuration, review, and future builds. Whether you can download an APK matters less than whether login, payments, permissions, updates, and native features still work after customers install the app.
Enter your Base44 URL in the form above and see what the wrapper looks like before you decide.
Related articles
