Can I submit a Base44 URL directly to the App Store?

No. Apple App Store Connect requires a signed native iOS archive (.ipa) and Google Play requires a signed Android App Bundle (.aab). AppNative compiles and signs both binaries from your Base44 app without requiring a Mac or Xcode.

Will Apple reject my Base44 app under Guideline 4.2?

Apple rejects plain web wrappers that behave like a browser bookmark under Guideline 4.2 (Minimum Functionality). Adding genuine native capabilities with AppNative — push notifications from Base44 functions, WidgetKit home-screen widgets, Live Activities, Face ID, native tab/safe-area handling and StoreKit 2 in-app purchases — gives reviewers real native functionality on launch.

AppNative › Blog › Publish Base44 App to App Store

How to publish a Base44 app to the Apple App Store and Google Play

Updated October 2026

Short answer: To publish a Base44 app to the App Store and Google Play, you need an Apple Developer account ($99/yr), a Google Play Console account ($25 once), and a native wrapper that compiles signed .ipa and .aab binaries. AppNative connects to your Base44 GitHub repo and live URL, automates Bundle ID registration, certificates, provisioning profiles, and TestFlight uploads, and compiles native capabilities (push notifications, widgets, Face ID, StoreKit 2 IAP) so your Base44 app passes Apple review without a Mac or Xcode.

1. Set up your Apple and Google developer accounts

Enroll in the Apple Developer Program at developer.apple.com ($99/year) and Google Play Console at play.google.com/console ($25 one-time fee). Always publish under your own accounts so you own your store listings, user reviews, and revenue.

2. Wrap your Base44 app into native iOS and Android binaries

Enable GitHub sync in Base44 and connect your repository to AppNative. Your Base44 entities, authentication, Row-Level Security rules, and backend functions stay untouched on Base44's backend while AppNative generates the native iOS (Swift / WKWebView) and Android (Kotlin) shell around your app.

3. Pass Apple Review Guideline 4.2 (Minimum Functionality) & 3.1.1 (Payments)

The two reasons AI-built web apps get rejected by Apple Review are:

Guideline 4.2 (Minimum Functionality): Apple rejects apps that look and act like a plain website inside a frame. In AppNative, enable native push notifications (triggered directly from your Base44 backend functions), Face ID biometric lock, WidgetKit home-screen widgets, iOS Live Activities, native safe-area theming, and offline caching.
Guideline 3.1.1 (In-App Purchase): If your Base44 app sells digital subscriptions, credits, or pro features via Stripe, Apple requires you to use StoreKit In-App Purchases inside the iOS app. AppNative's StoreKit 2 & Google Play Billing integration creates the subscription products in App Store Connect, displays a native paywall inside the iOS/Android app, and writes the entitlement back to your Base44 entities — while keeping Stripe active on the web.

4. Automate certificates, provisioning profiles, and TestFlight

Normally, shipping an iOS app requires a Mac, Xcode, Keychain CSR generation, distribution certificates, and per-extension provisioning profiles. AppNative automates all of this in the cloud: connect your App Store Connect API key once, and AppNative registers the Bundle ID, creates the certificates and profiles, compiles the archive on hosted macOS CI, and uploads the build straight to TestFlight.

5. Store listing, screenshots, and submission

Prepare your 6.7" and 6.5" iPhone screenshots (plus 13" iPad if tablet support is enabled), privacy policy URL, App Privacy nutrition labels, and demo login credentials for the Apple reviewer. AppNative can generate compliant screenshots, strip alpha channels from icons, and push your store metadata directly to App Store Connect and Google Play.

Want our team to handle the entire submission and App Review for you? See Done-For-You Base44 Mobile Apps.

Publish my Base44 app to the stores