One codebase, real store app
The iOS app loads your published Base44 URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for Base44 apps
Since February 2026 Base44 can generate its own store builds: a lightweight wrapper that shows your published app in a web view, which is enough for some internal tools and service apps. Its documentation names the limits, though: no Apple In-App Purchase or Google Play Billing, a bundle ID fixed by Base44 (com.base[app-id].app), files signed by Base44, no ads and no full offline mode. WebViewGold wraps the same published base44.app URL with your own bundle ID and signing keys and adds RevenueCat In-App Purchases, AdMob, an offline screen, biometric login and the Social Login Helper for Google. Every Publish in Base44 still updates the app immediately, and for login-first apps a demo account in the review notes does the rest.
Keep shipping from Base44
Publish again in Base44 and the app shows the new version immediately. Only changes to the native shell itself (icon, new native feature) need a store update.
Native features on top
Push notifications, offline screen, native sharing, biometric login, QR scanner, in-app purchases and deep links are single settings or one-line JavaScript calls.
App Store approval guarantee
Apple App Store approval guarantee – or your money back within 14 days. 96.4% of all WebViewGold apps get approved by the review teams on the first attempt.
What you need
- A published Base44 app on a public HTTPS URL (yourapp.base44.app or, better, your own domain)
- An Apple Developer Program ($99 per year) to submit to the Apple App Store
- Xcode on a Mac – or the WebViewGold Cloud Builder in your browser (no Mac needed)
- WebViewGold for iOS ($109 one-time, free updates)
- A privacy policy page, a 1024 × 1024 px icon and 30 to 60 minutes
With a good optimized version of your web app you can have a stunning mobile app within a couple of minutes. Additionally to that the customer service is very nice and very helpful! I can just recommend WebViewGold :-)
Base44 to App Store: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your Base44 app to a production URL
Click Publish in the Base44 editor. The app is hosted on a base44.app address and every later Publish updates the live version. Use the published URL, not the editor preview, in the app. Custom domain: Connect your own domain in the app settings (paid plans) and update the DNS records as shown. See why a custom domain before submission is worth it.
Make it store-ready
Add a privacy policy page, an account deletion option (if users can sign up), and remove builder badges or "download our app" banners. Run the free App Store readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
Get WebViewGold for iOS
One-time payment, free updates. You receive the ready-made Xcode project. If you do not own a Mac, activate the WebViewGold Cloud Builder and do everything in the browser.
Insert your URL and brand the app
Open Config.swift (or the Cloud Builder form) and paste your published URL. Set the app name, upload your icon, pick splash screen and status bar color. No coding needed.
Switch on native features
Enable push notifications, the offline screen, social-login handling, pull-to-refresh, biometric login or the QR scanner with single settings. Everything is optional.
Build and upload
In Xcode: Product → Archive → Distribute to App Store Connect. In the Cloud Builder: click Build, the upload to App Store Connect is done for you.
Create the App Store listing
In App Store Connect add name, subtitle, description, keywords, screenshots, privacy policy URL and the App Privacy answers. Add a demo account in the review notes if needed.
Submit for review
Apple reviews most apps within 24 to 48 hours. Answer reviewer questions in Resolution Center if any come up. Our approval guarantee covers you.
Base44-specific checks before you submit
These are the points that come up most often with Base44 projects (React front end generated by Base44 with Base44's own built-in database, authentication and integrations).
- Base44 apps often require login before any content is visible. Apple reviewers need a demo account: enter test credentials in the App Review notes, or allow guest browsing.
- Google login is blocked inside plain WebViews; WebViewGold's Social Login Helper fixes this without changes to your Base44 app.
- If you turn on Google, Microsoft or Facebook login, Apple Guideline 4.8 requires an equivalent login option that limits data to name and email, lets users keep their email private and does not track them. Your own email/password login does not reliably meet that bar, so also enable Apple login in the Base44 authentication settings (WebViewGold detects Sign in with Apple automatically). An app with only Base44's email login and no social login is not affected.
- Apps with user accounts must offer account deletion in-app (Apple 5.1.1, Google Play policy). Add a Delete account action in your Base44 settings page.
- Add a privacy policy page in Base44 and link it from the app footer; both stores require its URL.
- Made with Base44: Disable the Base44 branding in the app settings if your plan allows it, so no link to another platform sits inside your store app. More on builder badges.
Let Base44 do the store-readiness work
Paste this into Base44 and let it apply the changes reviewers look for. Review the result, then publish.
Prompt to paste into Base44
Prepare this app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper): 1. Add a Privacy Policy page and a Terms page with placeholder text I can edit; link them from the footer and settings. 2. Add a "Delete my account" button in the user settings that removes the user's data and account after a confirmation dialog. 3. Make sure the whole app is responsive from 320px to tablet widths, without horizontal scrolling, and that buttons are at least 44px tall. 4. Remove any "Made with Base44" badge, external promotional links and "Download our app" banners. 5. Show a clear retry message when data fails to load instead of a blank screen. 6. Set the page title to the app name (max 30 characters) and add a meta description.
App Store review: the rules that matter for Base44 apps
Apple reviews behavior, not tooling. Nobody is rejected for using Base44; apps are rejected for the points below.
- 4.2
Minimum Functionality
The app must offer more than a repackaged website. Responsive layout, native navigation and at least one native capability (push notifications, offline screen, native sharing, biometric login) make the difference. WebViewGold switches these on with one setting each.
- 2.1
App Completeness
No placeholder content, no dead links, no crashes. If content sits behind a login, provide a demo account in the App Review notes.
- 5.1.1
Privacy
A public privacy policy URL is mandatory. Apps that let users create accounts must also let them delete the account inside the app.
- 4.8
Login Services
If the app uses Google, Facebook or another third-party or social login for the user's account, it must also offer an equivalent login that limits data to name and email, lets users keep their email private and does not track them for advertising. Sign in with Apple is the safe way to meet this. An app that only uses its own email/password login is not affected.
- 3.1.1
In-App Purchase
Digital goods and subscriptions sold inside the app must use Apple's In-App Purchase. Physical goods and real-world services can keep Stripe or PayPal.
- 2.3
Accurate Metadata
Screenshots, description and app name must match what the app does. Do not mention other platforms or "beta" in the listing.
Native features your Base44 app gets in the iOS app
Every feature is optional and documented step by step in the WebViewGold for iOS documentation.
Push notifications
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call, permission prompt at the moment you choose.
DocumentationSocial Login Helper
Google and Facebook logins work inside the app; Sign in with Apple is handled automatically.
DocumentationUniversal Links
Links from emails (magic links, password resets) open directly in the app.
DocumentationIn-app purchases
App Store subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationOffline screen and fallback
A native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationLoading indicator and splash
Keep the launch screen until the web app is loaded, or show a native spinner.
DocumentationBiometric login
Face ID / Touch ID gate from a JavaScript call.
DocumentationQR and barcode scanner
Native scanner that returns the result to your web app.
DocumentationNative share sheet and haptics
Share dialog and haptic feedback from your web app.
DocumentationCustom CSS and JavaScript
Hide website-only elements and inject code when loaded inside the app.
DocumentationFeature guides for Base44 apps
Each guide shows the exact setup for your Base44 stack, with a prompt you can paste.
Push notificationsIn-app purchasesGoogle login and Sign in with AppleBiometric loginQR code and barcode scannerGeolocationAdMob adsOffline modeDeep linksNative share and hapticsFile downloads and camera uploadsIn-app ratingCustom CSS and JavaScriptNFC tag readerDocument scannerPrinting and AirPrintClipboard copy and pasteContacts accessVideo and audio playbackScreenshot protectionHealthKit and Health ConnectCalendar eventsFlashlightShare extensionWidgets and shortcutsApple Wallet passesNative storage and device IDMeta Audience Network adsNative tab bar and navigationSplash screen and loading indicatorSafe area and status barForce update and version checkExternal links and URL handling
Pre-flight checklist for App Store
Tick these off and the review is a formality. The free readiness check verifies the technical half automatically.
- HTTPS everywhere: App Transport Security blocks plain http:// content and invalid certificates.
- Responsive layout from 320 px to iPad widths. Apple also opens iPhone apps on an iPad during review.
- Privacy policy URL ready (a page inside your web app is fine).
- Account deletion available in the app if users can sign up.
- Demo login for the reviewer if content is behind authentication.
- No "Download our app" banners, no links to other app stores, no builder badges inside the app.
- A 1024 × 1024 px app icon without transparency and rounded corners (Apple adds the mask).
- Screenshots for the current iPhone sizes (and iPad if supported) taken from the real app.
- App name of 30 characters or fewer, a subtitle and keywords prepared.
- Export compliance answered (an app that only uses HTTPS qualifies for the standard encryption exemption).
Example: from Base44 project to approved app
Say you built a client portal for a home cleaning business with Base44: customers see upcoming visits, approve quotes, pay invoices through Stripe and message the team. You publish it, connect portal.yourdomain.com and wrap it with WebViewGold, with a demo customer account that already has two visits and an open invoice for the reviewers. Because invoices pay for a real-world service, Stripe stays and Apple does not ask for In-App Purchase. Push notifications announce when the cleaner is on the way, and the native file upload lets customers send a photo of a problem spot straight from the camera. Both stores approve the app, and every Publish in Base44 updates it without a resubmission.
Your first week after launch
- Keep the demo account alive and unchanged: if a teammate deletes its records, the review of your next app update fails.
- Send a push the first time a real visit or order status changes, so customers learn that notifications are worth keeping on.
- Reply to the first store reviews in App Store Connect and the Play Console; for a service business, those replies are part of customer care.
- Ask happy clients for a rating with rateapp:// after they approve a quote or pay an invoice.
- Test your account deletion page once more and confirm it removes the user's Base44 records, because both stores can check it at any time.
What you get with WebViewGold
A complete native app project, not a subscription. Everything below is included in the license and switched on with a setting.
- Complete Xcode project
- Push notifications
- Offline screen
- App icon & splash screen
- Share sheet & haptics
- Deep & universal links
- In-app purchases
- Free updates, white-label
Frequently asked questions
Does Base44 publish to the App Store or Google Play itself?
Since February 2026 it can: the Mobile app tab scans your app against the store guidelines and generates store files for a lightweight wrapper that shows your published app in a web view, which you upload with your own Apple and Google developer accounts (Builder plan or higher). Base44's documentation lists the limits: no Apple In-App Purchase or Google Play Billing, a bundle ID and package name that Base44 sets (com.base[app-id].app) and you cannot change, files signed by Base44, portrait only, no mobile ads and no full offline mode. For a login-first internal tool or a service app paid through Stripe that can be enough. WebViewGold is the better choice when you sell subscriptions or digital content, want AdMob, your own bundle ID and signing keys, an offline screen or native features such as biometric login, QR scanning and Universal Links.
Will the Base44 login work inside the app?
Email login works out of the box. For Google login enable WebViewGold's Social Login Helper, which opens the OAuth step in a browser window and returns to your app. If you also switch on Apple login in Base44 for Guideline 4.8, WebViewGold handles that flow automatically.
My Base44 app is behind a login. Is that a review problem?
No, as long as you provide a demo account in the App Review notes (App Store Connect) and in the Play Console app access section. Reviewers must be able to see the real content.
I already published with Base44's mobile option. Can I move the app to WebViewGold?
Usually yes, but plan it. Base44 sets the bundle ID and package name (com.base[app-id].app) and signs the files itself, so to update your existing listings with a WebViewGold build you keep that identifier and, on Google Play, request an upload key reset in the Play Console; otherwise the WebViewGold app becomes a new listing. If you are not live yet, decide before the first submission: with WebViewGold you choose an identifier under your own brand from day one and keep your signing keys. Your Base44 app stays as it is, since WebViewGold loads the same published URL.
Do I need a Mac to publish an iOS app?
Not with the WebViewGold Cloud Builder: configuration, build and upload to App Store Connect happen in the browser. If you own a Mac, the Xcode project works out of the box.
How long does Apple review take?
Most submissions are reviewed within 24 to 48 hours. First submissions and apps with logins sometimes get a question from the reviewer; answer it in Resolution Center and the review continues.
What if Apple rejects the app?
Rejections name the guideline and the reason, and you can resubmit as often as needed. WebViewGold comes with an App Store approval guarantee: if Apple rejects the app for a non-content reason, you get your money back within 14 days of purchase.
Base44 can publish mobile apps itself now. Why would I use WebViewGold?
Base44's built-in option also wraps your published app in a web view, which is fine for many apps. According to Base44's documentation at the time of writing, it offers no In-App Purchase, no mobile ads, a fixed bundle ID and portrait-only layout, while WebViewGold gives you complete Xcode and Android Studio projects with your own bundle ID, RevenueCat IAP, AdMob, the Social Login Helper and many more native features. Check the current Base44 docs and pick what your app needs.
Can I keep Stripe for payments in my Base44 app?
For physical products and real-world services (bookings, invoices, deliveries), yes, on both platforms. For subscriptions, credits or unlockable digital content, Apple requires In-App Purchase and Google generally requires Play Billing, which WebViewGold connects through RevenueCat; the US storefronts now allow more external payment options, so check the current regional rules.
Do I have to resubmit the app every time I change something in Base44?
No. The app loads your published URL, so content and feature changes you publish in Base44 are live in the app immediately. A new store version is only needed when the native shell changes, for example a new app icon or an added native feature.
What does it cost in total?
$109 one-time for WebViewGold for iOS (free updates) plus the Apple Developer Program ($99 per year). Optional: the Cloud Builder add-on ($349 per license, one-time) if you want to build in the browser without a Mac, or the Full Service package (from $698 per platform) where our team configures, builds and submits the app for you.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.