How to turn a Base44 app into an iOS and Android app
Median.co makes it easy to take your Base44 web app from the browser to the app stores. Convert your Base44 URL into a native iOS and Android app, add native mobile features like push notifications, haptics, and biometrics, then test your app using cloud-based builds and simulators or install it on a physical iPhone or Android device. When you're ready, publish to the Apple App Store and Google Play, without requiring a macOS computer, Xcode, or Android Studio with Median.
If you built a product in Base44 and now want it in the App Store or Google Play, the main question is not whether Base44 can build a web app. It already did that part.
The harder question is what happens after the web app works in a browser. You need a mobile app that opens cleanly, handles login, supports the device features your product needs, and gives Apple and Google enough app-like value to pass review.
Median turns your Base44 URL into a native iOS and Android app without asking you to rebuild the product in Swift or Kotlin. This is the website to app step. You still need to test the mobile version carefully, because a Base44 app that works in a desktop browser can behave differently inside a mobile WebView.
Use this guide when the real goal is the App Store or Google Play, an APK or test build, native features such as push notifications, or knowing whether the app is ready for store review.
Convert your Base44 web app into an iOS and Android app now
What is Base44?
Source: base44.com
Base44 is an AI app builder that turns plain-English prompts into working web applications, with databases, authentication, user management, and file storage handled for you.
What Base44 does not handle is the mobile side. App store distribution, native permissions, push notifications, signed builds, and store review are a separate job, and that job is what the rest of this guide covers.
What needs to be true before your Base44 app is ready for the app stores?
Your app can be a good mobile app, but the store build has to behave like more than a bookmarked website. Before you submit, check the parts Apple and Google reviewers will actually touch.
Your app should have:
A working login flow on mobile.
Navigation that fits a phone screen without hidden controls.
A clear reason to exist as an app, such as account access, repeat usage, push notifications, camera, location, or subscription access.
A stable app icon, launch screen, and app name.
Privacy policy and support links that match what the app collects and does.
Store screenshots that show the real product, not only the landing page.
A test account for reviewers if the app requires login.
If the app uses microphone, camera, location, file upload, payments, or subscriptions, test those flows on a device before you treat the build as ready. Those are the places where a browser preview can make the product feel done while the mobile version still is not.
Base44 to APK is not the same as an app store-ready Android app
Search data shows people looking for "Base44 to APK", "Base44 APK", and "Base44 downloader". That is a real testing need, but it can send you down the wrong path.
An APK helps you install and test an Android build. Google Play distribution needs a signed Android App Bundle, with package details, store listing assets, privacy declarations, and any required permissions. If the app will use subscriptions or in-app purchases, the store setup matters even more, because Google Play Billing has to be configured correctly.
Use an APK to answer: "Does this feel right on a phone?"
Use an app store-ready Android build to answer: "Can this be reviewed, distributed, updated, and monetized through Google Play?"
Median's App Studio covers both. It takes you from the URL to a mobile test build, then keeps you configuring the parts that affect a real launch.
Base44 to App Store: the iOS testing path
The iOS path is stricter than "download an app file and open it." You need Apple signing, provisioning, and a distribution route such as TestFlight or App Store submission. Median handles the build side in the cloud, so you do not need a Mac or Xcode to get a testable iOS app.
Test these flows before you submit:
Open the app from a clean install.
Log in and log out.
Use the primary action the app was built for.
Trigger each native permission prompt.
Test external links, deep links, and file downloads.
Confirm the app has a support path and privacy policy.
If the app is private, internal, or business-only, the distribution plan may differ from a public App Store launch. Make that decision early. It affects review, testing, and how you explain the app in the store listing.
How to build the native app from your Base44 URL
Step 1: Build your app in the Median App Studio
Start at median.co/app. Enter your Base44 URL as the "Website URL" and set your app name. An email address is required for ongoing access to your app in the App Studio, and a verification link arrives by email.
Step 2: Preview and test
Median's browser-based simulators preview your app on iOS and Android devices without leaving your web browser. Start by confirming the basic flows work inside the app rather than in a browser tab.
Step 3: Customize the native app
In the Branding tab, upload an app icon and splash screen and set theme colors. Interface Settings, Link Handling, Website Overrides, and Permissions control how the app behaves around your web content, and Native Navigation adds the app-like structure Apple and Google expect.
Median's native plugins add push notifications, haptics, biometric login, offline access, and other device features your Base44 app cannot reach from the browser.
Want to learn more about our plugins?
Launch a full-feature native app without native development!
Step 4: Test on real devices
Before submission, move past the simulator:
Use the public sharing link to give stakeholders access during testing.
Install test builds on physical devices. An Apple Developer account is required for iOS device testing.
Step 5: License and launch
The License tab covers plans by app functionality. Median also offers a publishing service where its team manages the store submission process end to end.
How to publish your Base44 app to the Apple App Store and Google Play
Once the native app is configured and tested, publishing means working through Apple's and Google's processes. The steps below assume you have already built the app in the Median App Studio and tested it in the simulators or on a device.
Publishing Base44 app to the Apple App Store
Apple's review process is rigorous, and your app needs to avoid looking like a bare web container. Follow these steps:
Register with the Apple Developer Program: Enrollment is typically $99 USD per year. Businesses register as an Organization, which requires a D-U-N-S number, so the brand name appears correctly in the App Store.
Create your app record: In App Store Connect, create a New App and match the Bundle ID to the one in your Median-built app.
Complete metadata and privacy details: Upload iPhone screenshot sets, fill in name, description, keywords, category, and support URL, and complete Apple's App Privacy section. If the app requires login, add demo credentials under App Review Information.
Upload the build: Connect your Apple Developer account in the Median App Studio using an App Store Connect API key. Median then builds a signed distribution IPA in the cloud and uploads it directly to App Store Connect for TestFlight and App Store submission. No Mac, Xcode, or Apple Transporter is required (see the upload documentation).
Submit for review: Apple typically responds within 24 to 48 hours, though it can take longer.
Publishing Base44 app to the Google Play Store
Create your Play Console account: Registration is a one-time $25 fee, and Google requires developer verification before publishing.
Complete the Play Console checklist: store listing metadata and graphics, a valid privacy policy URL, the Data Safety section, content declarations, permissions, target audience details, and app access instructions if login is required.
Upload your Android App Bundle: Generate the AAB from the Median App Studio (see the Android build documentation). Google no longer accepts APKs for new submissions.
Start the rollout: After review and policy checks pass, roll out to Production. New accounts can wait up to 7 days for the initial security review.
Note: Before submitting your app, download our free App Store Publishing Checklist to make sure it's ready for both the Apple App Store and Google Play review.
If you would rather not manage submission yourself
Median's publishing service has the Median team handle the entire submission: metadata, review feedback, and resubmissions. Median has published over 4,000 apps and, as of July 2026, maintains a 100% approval rate.
Case Studies
Discover how Median empowers companies to speed mobile app development, engage users, and reduce expenses.
Subscriptions and in-app purchases in a Base44 app
If the app sells digital subscriptions or paid features, the app stores require their own billing. Apple requires In-App Purchases for digital products, and Google Play requires Google Play Billing.
RevenueCat is Median's recommended path for subscriptions, and enabling it changes your build. The RevenueCat subscriptions guide covers the setup and what changes in App Store Connect and Google Play Console.
Frequently asked questions
Does Base44 have an iOS app?
Base44 is built for creating web apps. To run a Base44 project as an iOS app, the finished web app needs to be packaged as a native iOS app, configured, signed, and tested on real devices. Median handles that web to app step from your Base44 URL.
Can I publish a Base44 app to Google Play?
Yes. The easiest way to publish your Base44 app to Google Play is with Median.co. If your mobile app meets Google Play's requirements and the build is prepared correctly, you're ready to publish. A browser-ready Base44 app is not automatically ready for Google Play. You'll still need app signing, store assets, permissions, privacy details, and a build format accepted by Google Play.
Do I need to export my Base44 app's code first?
No. Median does not need an export of the Base44 code. It needs the published Base44 URL, which the native app loads directly, so the app stays in sync with the version you keep editing in Base44.
Can I turn a Base44 app into an APK?
Yes. An APK is useful for Android testing, but it is not the whole publishing plan. For Google Play, you need an app store-ready Android App Bundle plus the correct Play Console setup.
What should I test before submitting to the app stores?
Test login, mobile navigation, forms, payments, camera and microphone access, file upload, push notifications, deep links, app icons, splash screens, privacy links, and any flow that depends on a third-party service. The parts that feel fine in a desktop browser are often where mobile review issues start.
How do I get a UDID for iOS test installs?
To install a test build on a specific iPhone, you may need the device's UDID. The fastest route is Median's UDID tool, which reads it from the device in the browser. The UDID goes into your Apple provisioning setup so the test build can install on that device.
Do Base44 apps need deep linking testing?
Yes. Before publishing, use Median's free Deep Linking Validator to test your Base44 app's Universal Links and Android App Links. It checks your AASA and assetlinks.json configuration to help identify issues before App Store and Google Play submission.
Enter your Base44 URL and test the mobile app version
Related articles
