Base44 to App Store & Google Play: What Actually Works (2026)

Your Base44 app is live at yourapp.base44.app — auth works, the data model holds up, people use it in a browser. Now you want it on phones, and you've typed some version of “base44 to app store”into Google. Here is the honest map, including the part where Base44's own tooling is the right answer.

What Base44 itself now offers

As of 2026 Base44 has a store path built into the editor: a Publish → Mobile app tab that scans your app against App Store and Google Play guidelines, lets the AI chat fix flagged issues, and then generates store files — an IPA for App Store Connect (you provide your Issuer ID, Key ID, Team ID and a .p8 API key) and files for Google Play. Their docs are upfront about the mechanics: the mobile app “runs your published Base44 app inside a secure web view … a lightweight native wrapper around your web app”.

Two constraints from those same docs decide whether it's enough for you:

• No push notifications, no full offline.Their wrapper “does not currently support native-only features such as push notifications or full offline mode.”
• Downloading the store files needs the Builder plan or higher. The scan is free; the files are not.

If you're already on a paid Base44 plan and your app doesn't need push, their built-in path is genuinely the simplest option — one tool, no third party. Use it. The rest of this guide is for everyone who hit one of those two walls, or who needs something Base44 doesn't build at all.

The wrapper route with push, from just your URL

Our route takes the same input — your published .base44.app URL or custom domain — and returns signed binaries. No export, no GitHub, no Base44 login shared with us. The differences that matter:

• Push notifications work. The Android wrapper ships with OneSignal wired in — add your OneSignal App ID in the wizard and the APK/AAB comes out push-ready. This is the single most common reason people outgrow a bare webview wrapper.
• Native shell elements are included — splash screen, pull-to-refresh, native navigation chrome. Store reviewers reject bookmark-in-a-box apps under Guideline 4.2; native surface area is the concrete thing that distinguishes an app from a bookmark.
• Android is free to try. Your first build costs nothing and produces a real, installable, signed APK (with a splash watermark). You can put it on a device before deciding anything.
• Windows exists here. The same URL can come back as a Windows installer (Electron-based .exe) — Base44 has no desktop story at all.

Because your Base44 app keeps living at its URL, the same property their docs advertise holds on our wrapper too: publish a change in Base44 and the installed app shows it — no store re-submission for content and design changes.

What no vendor can remove

Three requirements survive every route, and any page that hides them is lying to you:

• The developer accounts are yours.Apple's program is $99/year; Google Play's registration is a one-time $25. Base44's docs say it plainly — you set up and pay for both, and submissions happen in your dashboards. Same here.
• iOS signing needs your certificate. Our iOS builds run on real Apple silicon and are signed with the .p12 you upload — the wizard verifies the certificate and password before any build starts, so a bad p12 fails in seconds, not after a queue.
• Store review risk is real on every platform. Guideline 4.2 rejections happen to webview apps from every vendor — Base44's scan, our native chrome, and honest store listings all reduce the risk; nothing eliminates it. When one of our builds fails, the credit refunds automatically. When a store rejects an app, that's between you and the store — on every service.

Which route fits you

Try it with your Base44 URL

Paste your published URL into the wizard, pick Android, and you'll have a signed APK on your phone in a few minutes. The first one is free, and if a build ever fails you see the actual reason and the credit comes back on its own.