Base44 Limitations on iOS — and How Each Is Fixed

The Limits of Base44 for Mobile Monetization

## What Base44 Can't Do (Yet) Base44 is brilliant at shipping a web app fast. But the moment you want a real iOS product on the App Store, you hit walls: - **No native iOS build pipeline.** Base44 outputs a web app. The App Store accepts native binaries. You're stuck unless you use a native app, rebuild, or hire native engineers. - **No App Store submission.** Apple Review, screenshots, metadata, privacy nutrition labels, age ratings — Base44 doesn't touch any of it. - **No StoreKit / in-app purchases.** Stripe works on the web. Apple requires StoreKit for digital goods inside an iOS app. Base44 ships neither the SDK nor the server-side receipt validation. - **No Apple Push Notifications.** Web push doesn't exist on iOS Safari for installed apps. You need APNs, a push certificate, and a token registration flow. - **No native analytics.** No install attribution, no session events from the App Store binary, no crash reporting tied to your Base44 backend. - **No Apple Small Business Program enrolment.** Most pre-PMF founders qualify for the 15% rate (vs 30%) — but Base44 doesn't guide you through it. None of this is Base44's fault — it's out of scope. But it's also why most Base44 apps never reach the App Store.

How to Implement Limitations & Fixes in Base44 using Wanilla

## How Wanilla Closes Every Gap We're the guided launch partner for Base44 founders. You keep building in Base44. Wanilla builds your product into an iOS app with native features and prepares an honest App Store submission, ready for you to submit from your own Apple Developer account. No native code to maintain. You ship product; we ship the native plumbing. [lin slug="base44-in-app-purchases" label="See how we handle Base44 in-app purchases →"] [lin slug="base44-push-notifications" label="See how we handle Base44 push notifications →"] [lin slug="base44-app-store-publishing" label="See how we handle App Store publishing →"] [lin slug="lovable-revenuecat-alternative" label="Why most Base44 founders skip RevenueCat →"]

How Wanilla builds a native app around your Base44 product with Limitations & Fixes

Code Integration Example

What Base44 genuinely cannot do, and the fix for each

Base44 is a web application builder. Everything it produces runs in a browser, served from a URL. That is the root of every limitation below — none of them are bugs, they are the boundary of the platform.

No App Store build. Base44 has no native export and no Xcode project, so there is nothing to upload to App Store Connect. Fix: your published Base44 URL is loaded inside a native iOS app we build with you, ready for you to submit from your own Apple Developer account.
No in-app purchases. Stripe checkout in a web view is rejected under App Store guideline 3.1.1 for digital goods. Fix: native StoreKit 2 products are configured in App Store Connect and the paywall is rendered natively, with your Base44 database updated over the bridge when a purchase completes.
No receipt or entitlement storage. The built-in database has no concept of an Apple transaction. Fix: a small entitlements table is added to your Base44 data model and written to on purchase, renewal and restore, so the web app and the iOS app agree on who is subscribed.
No push notifications. Web push does not reach the iOS lock screen from a thin web app in a reliable way. Fix: Apple Push Notification service is configured with your APNs key, and sends are triggered from your Base44 backend.
No biometric login. There is no native module system, so LocalAuthentication is unavailable. Fix: Face ID and Touch ID are handled in the native layer and unlock the existing Base44 session, so your authentication logic does not change.
Guideline 4.2 rejection risk. Apple rejects apps that are only a website with no native value. Fix: the build ships genuine native behaviour — offline handling, native navigation, haptics, share sheet, push and StoreKit — which is what reviewers look for. Apple reviews and makes the final decision.
No Apple commission control. Fix: enrolment in Apple's Small Business Program takes commission from 30% to 15% for the first million dollars, and we help you complete the enrolment before your first release.

Nothing in your Base44 project is rewritten. Any change to what the app does ships as a new build that Apple reviews.

// Example: Verifying a Limitations & Fixes purchase from Base44
fetch("https://api.wanilla.co/v1/verify-purchase", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    platform: "base44",
    receipt: transactionReceipt,
    product_id: "pro_monthly"
  })
})
.then(res => res.json())
.then(data => {
  if (data.valid) {
    // Unlock premium features
    enablePremiumAccess();
  }
});

Related Guides

Once you've set up Limitations & Fixes, you might also want to add Adapty Alternative to Base44 or add App Store Publishing to Base44.

Working with other AI builders? See our guide on Limitations & Fixes for Lovable or Limitations & Fixes for Replit.

Explore our full breakdown of Base44 App Integration.

How to publish your Base44 app with Limitations & Fixes

Ready for you to submit from your own Apple Developer account within 4 working days. Apple's review time and decision are outside our control$2,995 one-off + $199/month — we build the native app with you and support your launch

1
Connect your Base44 app
Share the live URL of your Base44 app. We review the product and agree the scope with you.
2
Wire up native Limitations & Fixes
Wanilla builds the iOS app with native Limitations & Fixes support, working to Apple Guideline 4.2.
3
Prepare the App Store listing
Bundle ID, App Store Connect record, privacy nutrition labels, screenshots, description and keywords are prepared for submission.
4
Configure pricing and paywall
Subscriptions and in-app purchases are created in App Store Connect and wired to StoreKit 2. Any change to how the app works goes to Apple as a new version.
5
Submit from your account and go live
Your app is ready to submit from your Apple Developer account within 4 working days. If Apple raises an issue, Wanilla helps you fix it and prepares a new version. Apple makes the final decision.

Base44 + Wanilla vs. Custom Native Development

Feature	Base44 Web App	Custom React Native	Base44 + Wanilla
Development Time	Minutes (AI Generated)	Weeks / Months	Minutes
App Store Ready	No	Yes	Yes
Limitations & Fixes Support	❌ Web only (Stripe)	✅ Native IAP	✅ Native IAP
Developer Cost	Low	Very High	Low (SaaS)

Frequently Asked Questions

Is Base44 actually capable of producing an iOS app?▾

Base44 produces a web app. It can be installed as a PWA, but Apple doesn't accept PWAs in the App Store and PWAs can't use StoreKit, APNs, or native APIs. To list on the App Store you need a native iOS binary — that's what Wanilla provides.

Can I use Stripe inside a Base44 iOS app?▾

No. Apple's App Store guidelines require StoreKit for digital goods and subscriptions inside an iOS app. Stripe is fine for physical goods or web-only products. Wanilla's StoreKit bridge lets your Base44 frontend stay the same while purchases route through Apple.

Why doesn't Base44 support push notifications on iOS?▾

iOS push requires APNs (Apple Push Notification service), a push certificate signed for your bundle ID, and a token registration flow inside a native app. None of that is possible from a web app. Wanilla configures APNs, ships the native registration code, and syncs tokens back to your Base44 backend.

Can I submit my Base44 app to the App Store myself?▾

Yes — in fact, you publish from your own account and submit it yourself. Doing it completely alone, you'd need an Apple Developer account ($99/year), a native iOS build, App Store Connect setup, screenshots at multiple device sizes, a privacy nutrition label, an age rating, and a response plan for App Review. We've seen first-time submissions take 4–8 weeks. Wanilla prepares everything with you to compress that to under 2 weeks, ready for you to submit from your own Apple Developer account.

What about Apple Review rejections?▾

Common Base44-app rejections: Guideline 4.2 (minimum functionality, app is 'just a website'), Guideline 3.1.1 (using non-StoreKit payments for digital goods), and metadata issues. Wanilla builds your product into an iOS app with native features, prepares an honest App Store submission, and helps you respond to App Review.

Do I qualify for Apple's Small Business Program?▾

If your business earned under $1M from the App Store in the prior calendar year, yes — and Apple's commission drops from 30% to 15%. Wanilla helps you enrol on Day 1 so you don't leave revenue on the table.

Will I have to migrate off Base44 later?▾

No. We build your product into an iOS app with native features and prepare an honest App Store submission. We're the native layer, not a replacement.

How long does the whole launch take?▾

Wanilla prepares your submission within 4 working days, ready for you to submit from your own Apple Developer account. Apple reviews and makes the final decision, and review time is outside our control. Book a Free Launch Review and we'll give you a tailored timeline.

Official Resource

Base44 Documentation — Official Base44 developer documentation

Book a Free Launch Review

Book a free launch review. Ready for you to submit from your own Apple Developer account within 4 working days. Apple's review time and decision are outside our control.

Or see the guided launch offer — $2,995 + $199/month

Samuel Olsson

Co-founder, Growth, Wanilla

Connect on LinkedIn