Key takeaways
- Base44 offers two iOS routes: its own IPA export from the Mobile app tab (Builder plan or higher) or a native wrapper such as WebViewGold that loads your published Base44 app.
- Base44's export is a web view with optional push – quick, but without StoreKit, offline mode or an editable Info.plist, which matters for Guidelines 4.2 and 3.1.1.
- Whatever the route, App Review expects a sign-in it can complete, Sign in with Apple next to Google, In-App Purchase for digital content and account deletion in the app.
- WebViewGold, made by our team, is a one-time purchase Xcode project; appsubmitter.io handles signing, the App Store listing, the submission and the conversation with App Review.
Our recommended solution
Turn your Base44 app into a real iOS app with WebViewGold
WebViewGold wraps the Base44 web app you already have in a native Xcode project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at the App Store look for. Built by our own team, and we submit WebViewGold apps all the time.
How to convert Base44 to an iOS app: the short answer
To convert Base44 to an iOS app, you either generate an IPA in Base44's own Mobile app tab or load your published Base44 URL in a native Xcode project such as WebViewGold, then submit the result from your own Apple Developer account. The first route is faster; the second gives you the native features, In-App Purchase and control that App Review tends to reward.
Both routes start from the same place, because Base44 – the Israeli AI builder that Wix acquired in June 2025 – builds web apps. You get a React frontend with React Router, Vite, Tailwind CSS and shadcn/ui, plus a managed backend: a NoSQL database, built-in authentication and Deno-based backend functions. The app runs in the browser at yourapp.base44.app or on a custom domain (Starter plan and up). Code leaves Base44 through two-way GitHub sync (Builder plan and up) or a zip export, but even an ejected copy keeps the Base44 SDK as its interface to the backend. A native rewrite therefore either keeps talking to Base44 or replaces the backend – which is why most teams ship the hosted web app inside a native shell.
Four routes from Base44 to the iPhone, compared
| Route | What you ship | Strengths | Watch out for |
|---|---|---|---|
| Base44 Mobile app tab | An IPA: a web view that opens your published app, optional push | No Mac or Xcode; guideline scan with AI fixes; permissions and purpose strings set for you | No StoreKit, no full offline mode, Info.plist not editable; start page and bundle ID chosen by Base44; Builder plan or higher to download |
| WebViewGold | Your own Swift Xcode project that loads your Base44 URL | Native modules from push to StoreKit; one-time purchase; Cloud Builder if you have no Mac | You configure and update the project; In-App Purchase needs the Extended license |
| Capacitor or a native rebuild | A project built around exported code or written from scratch | Full control over every native API | Developer time; Capacitor's docs say loading a remote URL via server.url is not intended for production; the Base44 SDK stays your backend interface |
| Progressive web app | Your web app with the manifest Base44 generates automatically | No review, instant updates; web push for Home Screen web apps since iOS 16.4 | No App Store presence, fewer device features |
Base44's own documentation lists Capacitor, PWABuilder and Trusted Web Activities as options outside the platform, managed by you. If your users only need the app on a few home screens, the PWA route is honest and free of review. If you want App Store presence, the real choice is between the first two rows – and it usually comes down to payments and native features.
Want your Base44 app in the App Store without the trial and error?
Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.
What you need before you start
- Apple Developer Program membership as an individual or organization. Organizations need a D-U-N-S Number, and the legal entity name becomes the seller name, so it should match the business behind the app.
- A production URL. Base44's export works with the default base44.app address; for a wrapper, a custom domain keeps branding, links and seller identity consistent.
- Xcode – or a cloud build. Base44's generator and WebViewGold's Cloud Builder both run without a Mac; building the WebViewGold project yourself needs Xcode.
- Legal pages: privacy policy and terms reachable before sign-up, plus a support URL for the listing.
- For Base44's export: an App Store Connect API key (Issuer ID, Key ID, Team ID,
.p8file). Base44 recommends the Admin role if generation fails with a permission error, and every IPA generation creates a new iOS Distribution certificate, so revoke unused ones when Apple's limit is reached. - A review account that signs in with email and password and holds realistic data.
Step 1: Make the Base44 web app feel at home on an iPhone
Whichever shell you choose, the web app is what the reviewer touches. Ask the AI chat to:
- Respect the notch and home indicator:
viewport-fit=coverin the viewport meta tag andenv(safe-area-inset-*)padding on fixed headers and bottom bars. - Hide website furniture inside the app – long footers, "add to home screen" hints, the Base44 badge (removable from the Starter plan up).
- Recognize the app through a custom user-agent suffix and use it for layout and native integrations only, never to decide which features exist.
- Open payment providers, social profiles and documents outside the app view.
- Use Base44's custom login pages, and keep
/forgot-passwordand/reset-passwordat the paths the AI created – the reset email links to that exact path. - Add a Delete account option in account settings. Guideline 5.1.1(v) requires it, and Base44's login setup doesn't create one for you; see account deletion in WebView apps.
Step 2: Build the iOS shell with WebViewGold
WebViewGold is a ready-made Xcode project in Swift, built by our team and sold as a one-time purchase (the Extended license covers In-App Purchases). Base44 is one of the builders its documentation names.
- Enter your Base44 production URL in
Config.swift– never a testing link, which shows unpublished changes and test data. - Set bundle ID, name, icon and splash screen. Unlike Base44's export, the bundle ID is yours.
- Switch on the modules your journey needs and add a purpose string to
Info.plistfor each permission they use. - Configure URL handling so payment links, documents and external sites open outside the web view.
- Build on your Mac, or let the Cloud Builder configure, build and upload in the browser; our team also offers a done-for-you setup.
| Typical Base44 app | Modules worth switching on |
|---|---|
| Bookings and class schedules | Push reminders from Base44 events, QR check-in, calendar entries |
| Internal tools and CRMs | Face ID re-login, native sidebar, document scanner, offline screen |
| Courses and memberships | StoreKit In-App Purchases, push for new lessons, native rating dialog |
| Fitness and habit trackers | Push, a Home Screen widget, the HealthKit plugin (Base44's export doesn't support HealthKit) |
| Marketplaces and directories | Universal links for shared listings, native share dialog, push for messages |
One Base44 caveat: its domain documentation says Base44 serves the /.well-known path itself. Before relying on universal links, confirm with Base44 support that your apple-app-site-association file can be served there; custom URL schemes are the fallback.
The shortcut from Base44 to the App Store
WebViewGold: your Base44 app, native on iOS
Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:
- Push notificationsOneSignal or Firebase, for real, personal events
- Native offline screenNo browser error pages when the connection drops
- Native splash screenApp-like start instead of a loading web page
- Deep linksLinks open the right screen inside the app
- QR & barcode scannerDevice features the website alone can't offer
- In-app purchasesNative purchase flows where the store requires them
No tool guarantees an approval: Apple still judges what your app offers. Use the native features in your main user journey – our App Specialists review your WebViewGold app before it goes to the App Store.
Step 3: Sign-in, payments and privacy the way App Review expects
Sign-in
If people can sign in with Google, Microsoft or Facebook, Guideline 4.8 expects an equivalent privacy-focused option – in practice Sign in with Apple, which Base44 has supported since February 17, 2026. WebViewGold handles Apple's sign-in page (appleid.apple.com) automatically. Google is harder, because it blocks its OAuth page inside embedded WebViews. The clean native fix is ASWebAuthenticationSession or Google's Sign-In SDK – custom code in the Xcode project – but Base44 documents no way to hand a session obtained that way to the web view. For most Base44 apps the practical answer is email and password plus Sign in with Apple in the app, with Google kept for the website. Sending people to Safari to sign in satisfies Google, yet Apple calls that a poor experience under Guideline 4. Base44's default Google login also shows base44.com on the consent screen; your own Google OAuth client (Builder plan, custom domain) shows your domain. More in Guideline 4.8 for WebView apps.
Payments
Digital content and features need In-App Purchase under Guideline 3.1.1; physical goods and real-world services may use Stripe or Base44 Payments. Base44's export can't run StoreKit, and its docs say RevenueCat and Capacitor purchase plugins can't reach its native layer. WebViewGold's In-App Purchases module starts StoreKit purchases from your web app, through RevenueCat by default or a manual setup; pass the signed-in user's ID so a Base44 backend function can record the entitlement. The storefront rules are in 3.1.1 for WebView apps.
Privacy
Fill in App Privacy details for everything the Base44 app and your SDKs collect: account data, user content, push tokens, analytics. Every permission needs a purpose string. Base44's export generates them – since July 26, 2026 every iOS build includes them – while in WebViewGold you write them yourself, for example NSCameraUsageDescription for uploads and scanning and NSFaceIDUsageDescription for Face ID.
Step 4: TestFlight, App Store listing and Notes for Review
- Upload the build and install it from TestFlight on an iPhone and an iPad.
- Walk the review path: fresh install, sign-up, sign-in with the review account, password reset, purchase, account deletion and Airplane Mode.
- Create the listing with screenshots of the real app, a description that only promises what it does and a support URL.
- Write Notes for Review that name every native feature and where it lives, the review account, and which content is web-based and updated without a new build.
- Submit, then hold back new features until approval – new functionality ships with the next reviewed version, as our article on Base44 apps and Guideline 5.6 explains.
App Store rejections Base44 apps run into – and the fixes
| Guideline | Base44-specific trigger | Fix |
|---|---|---|
| 4.2 Minimum Functionality | A shell that opens one URL, with push as its only native feature | Native features in the core journey – see 4.2 for WebView apps |
| 4.3 Spam and 4.2.6 | Default theme and AI-generated logo shared by many apps; an agency submitting client apps from its own account | Your own design; publish from the client's own account |
| 2.1 App Completeness | Private visibility, review data that only exists in Test data, Google sign-in that fails | Access for the review account, Production data, email and password |
| 4.8 Login Services | Google, Microsoft or Facebook login without Sign in with Apple | Enable Apple under Settings → Authentication |
| 3.1.1 In-App Purchase | Stripe checkout for subscriptions, credits or premium features | In-App Purchase through the wrapper |
| 5.1.1(v) Account deletion | Sign-up without a way to delete the account | A Delete account option in settings |
| 5.6 Code of Conduct | Features published after approval | Release features together with reviewed versions |
appsubmitter.io takes over the time-consuming part: certificates, provisioning profiles and code signing, a CI/CD pipeline with fastlane, the App Store Connect listing, App Privacy details, an AI-powered pre-submission check reviewed by an App Specialist, the Notes for Review and every message with App Review. We publish in your own developer account and work as members of your team, as Guideline 4.2.6 expects. Code changes are quoted separately upfront, and your app doesn't have to be finished when you book. Book the iOS service or start with a free consultation call.
Checklist before you submit
- You chose a route: Base44's IPA for a simple app, or a native wrapper when you need StoreKit, offline handling or more device features.
- The shell loads your production Base44 URL – ideally on a custom domain – never a testing link.
- Safe areas, website footers, the Base44 badge and external links have been adapted for the app.
- The review account signs in with email and password and has realistic data in Production.
- Sign in with Apple appears wherever Google, Microsoft or Facebook login does.
- Digital content is sold with In-App Purchase; Stripe or Base44 Payments only cover physical goods and services.
- Users can delete their account inside the app.
- Every permission has a purpose string, and App Privacy details match what the app collects.
- The build was tested from TestFlight on an iPhone and an iPad, including Airplane Mode.
- The Notes for Review list every native feature, where it lives and the review account.
Frequently asked questions
Can I publish a Base44 app on the App Store?
Do I need a Mac to convert Base44 to an iOS app?
Is Base44's own IPA export enough to pass App Review?
Can I update my Base44 app without resubmitting?
How long does App Store review take?
What does it cost to turn a Base44 app into an iOS app?
Recommended solution
From Base44 to the App Store: WebViewGold + appsubmitter.io
- 1 Build with WebViewGold Turn your website into native iOS and Android projects.
- 2 Add native value Push, offline screen, deep links or scanning in your main flow.
- 3 We submit it Our App Specialists submit and talk to the review team.
WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.
Sources and further reading
- Base44 Docs – Submitting your app to app stores
- Base44 Docs – Creating and using your app on mobile (PWA, export, wrappers)
- Base44 Docs – App code overview
- Base44 – Product changelog
- Apple – App Store Review Guidelines, 4.2 Minimum Functionality
- Apple – App Review: review times, appointments and appeals
- Google Developers Blog – OAuth changes for embedded webviews (June 29, 2021)
- Capacitor – Configuration reference (server.url)
Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.