Key takeaways
- Base44 can generate an AAB itself (Builder plan or higher), but the package name com.base[app-id].app and the signing setup are fixed, and Play Billing and full offline mode aren't supported.
- A WebViewGold Android Studio project gives you your own package name, Play Billing, Custom Tabs for external sign-in pages, offline handling and device features; a TWA suits Base44 apps that work well as a PWA.
- New personal Play Console accounts need a closed test with at least 12 testers for 14 consecutive days, and new apps and updates must target API 36 since August 31, 2026.
- Plan for Google's WebView spam rule, Data safety, account deletion in the app and on the web, and Play Billing for digital goods – appsubmitter.io can run the Play Console side.
Our recommended solution
Turn your Base44 app into a real Android app with WebViewGold
WebViewGold wraps the Base44 web app you already have in a native Android Studio project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at Google Play look for. Built by our own team, and we submit WebViewGold apps all the time.
How to convert Base44 to an Android app
To convert Base44 to an Android app, choose one of three packaging routes – Base44's own Google Play files, a WebView wrapper project such as WebViewGold, or a Trusted Web Activity (TWA) – and publish the resulting Android App Bundle (AAB) from your own Google Play Console account. Packaging takes hours; Google Play's account checks, closed testing and policy forms take weeks, so start those first.
Whatever you package is your published Base44 web app: a React frontend on Base44's managed backend, served from yourapp.base44.app or a custom domain. Android sees a website in a container, which is why Google's rules on WebViews, user data and payments shape the decisions below more than any line of code.
Google Play Console first: account, verification and closed testing
- Developer account. You register in Play Console with a one-time registration fee, as a personal or an organization account; organizations need a D-U-N-S number.
- Verification. New personal accounts also verify a physical Android phone through the Play Console mobile app.
- Closed testing. Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for 14 consecutive days before applying for production access. Organization accounts aren't covered. Our guide to the 12-tester rule shows how to pass it the first time.
- Production access. Google says this review usually takes seven days or less – and every production release is still checked against policy.
A Base44 app has an advantage during the test: every web publish reaches your testers immediately. Still ship a few new builds during the 14 days. Google expects testing that leads to fixes, and web-only changes never show up as releases in Play Console.
Want your Base44 app in Google Play 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.
Base44 AAB, WebView wrapper or TWA: choosing the Android route
| Base44 Google Play files | WebViewGold for Android | Trusted Web Activity | |
|---|---|---|---|
| What it is | A web view around your published app, generated in the Mobile app tab | An Android Studio project that loads your Base44 URL, with native modules | Your PWA full screen in the user's browser, packaged with PWABuilder or Bubblewrap |
| Package name | Fixed: com.base[app-id].app | Your choice | Your choice |
| Signing | Configured by Base44, not changeable | Your upload key plus Play App Signing | Your key (PWABuilder can generate one) plus Play App Signing |
| Push | Via your own Firebase project | OneSignal, Firebase or Pushwoosh | Web push through notification delegation |
| Digital purchases | No Play Billing | Google Play Billing module (Extended license) | Play Billing through the Digital Goods API |
| Google sign-in | Needs the Play App Signing SHA-256 added in Base44 | Chrome Custom Tabs via URL handling – test that the Base44 session reaches the app | Runs in the browser, so the WebView block doesn't apply |
| Offline | No full offline mode | Fallback page with a reconnect button | Whatever your service worker provides |
| You need | Builder plan or higher | Android Studio or the Cloud Builder | A Digital Asset Links file on your domain |
Base44's documentation names Capacitor, PWABuilder and TWAs as options outside the platform and generates a web app manifest for every app, so the TWA route is realistic – note that it documents the manifest, not a service worker. Check one more detail first: its domain docs say Base44 serves the /.well-known path itself, while a TWA only runs without a browser bar when /.well-known/assetlinks.json on your domain lists your package and signing key. Confirm with Base44 support that your file can be published there.
Route 1: Base44's Google Play files, step by step
- In the editor, open Publish → Mobile app → Check Your App, run the scan against the Google Play guidelines and let the AI chat fix critical issues.
- Under Build Stores Files → Create Google Play files, review the logo – changing it here changes your app's logo too – and for push turn on Add push notifications and upload
google-services.jsonand a service account key from your own Firebase project. - Generate and download the AAB, then create the app in Play Console with the package name
com.base[app-id].app; the app ID appears in your editor URL. - If the app offers Google login, copy the SHA-256 fingerprint of the app signing key from Play Console and add it in Base44 under More actions → Add Google Play SHA.
- Upload the AAB to the closed testing track and invite your testers.
Know the limits before you commit. Base44 sets permissions through its AI scan and doesn't let you edit them; a rejection for a missing billing permission is something only Base44 support can fix; and if you published an Android app for the same brand before, the fixed package name and signing key won't match it, so Base44 advises creating a new store listing. Push only reaches existing users after you ship updated files with notifications enabled.
Route 2: WebViewGold – your own Android Studio project
WebViewGold is the website-to-app product our team builds: an Android Studio project you point at your Base44 URL, configure in one file and build into an AAB – or build in the Cloud Builder without a local Android Studio setup. It's a one-time purchase, you choose the package name and keep the signing keys, and Base44 is one of the builders its docs name. The modules that matter most for Base44 apps on Android:
- Navigation: a Material navigation drawer or Material 3 bottom bar for your main pages.
- Push: OneSignal, Firebase or Pushwoosh, with deep links into the right page.
- Payments: Google Play Billing for digital goods and subscriptions (Extended license).
- Uploads and scanning: the document scanner adds a Scan document option to the file upload dialog; QR and barcode results go straight to your web app.
- Links and sign-in: URL handling decides which links stay in the app, open in Chrome Custom Tabs or go to the browser; BiometricPrompt protects re-entry.
- Offline: a fallback page with a reconnect button instead of Chrome's error screen.
- More: Health Connect, NFC, geolocation and the native Google Play review dialog.
Start from the latest WebViewGold release – it is updated regularly – and confirm in the bundle you upload that it targets API level 36.
The shortcut from Base44 to Google Play
WebViewGold: your Base44 app, native on Android
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: Google still judges what your app offers. Use the native features in your main user journey and keep proving that you own the website – our App Specialists review your WebViewGold app before it goes to Google Play.
Android details that make or break a wrapped Base44 app
| Check | Why it matters | What to do |
|---|---|---|
| Target API 36 | Required for new apps and updates since August 31, 2026 | Verify the uploaded bundle – see our target API guide |
| Notification permission | Android 13 and later ask for POST_NOTIFICATIONS at runtime | Ask when someone turns on reminders, not at first launch |
| Back gesture | Predictive back is on by default when you target API 36 | Back walks through Base44 pages instead of closing the app |
| Edge-to-edge | Android 15 and 16 draw content behind the system bars | Safe-area padding in the Base44 layout |
| File uploads | A WebView only opens a chooser if the app implements onShowFileChooser | Test every upload field with camera and files |
| Google sign-in | Google blocks OAuth in embedded WebViews | Custom Tabs or Credential Manager, then check that the session reaches the app |
| App Links | Verified links need assetlinks.json on your domain | Confirm Base44 can serve it, otherwise use a custom scheme |
Google Play policies a Base44 app has to pass
Webviews and Affiliate Spam – and limited functionality
Google doesn't allow apps whose primary purpose is to show a website without its owner's permission. Your own Base44 app makes that case more easily on your own domain: a developer name, contact email and store website that match it show the connection, a bare base44.app subdomain says little. Permission alone isn't enough, though – an app that is "static without app-specific functionalities" fails the limited functionality rule. Details in our WebView spam guide.
Data safety and account deletion
Data collected by web content your app controls belongs in the Data safety form, together with push tokens and SDK data. If people can create accounts, Google wants deletion inside the app and a public web page where they can request it without the app, linked in the form. Base44 builds neither for you, so ask the AI chat for a Delete account option in settings and a deletion request page outside the login – our account deletion guide lists what the page needs.
Payments and consistent behavior
Digital goods and subscriptions sold in the app go through Google Play Billing, with country-specific alternative billing programs as exceptions; physical goods and services can keep Stripe or Base44 Payments, which is powered by Wix. Base44's export can't run Play Billing, so selling digital content in the app means a wrapper with a billing module. And because a Base44 app changes with every publish, keep Google's Deceptive Behavior policy in mind: the app must behave the same for reviewers and regular users.
From closed test to production: a release plan
- Upload the first AAB to internal testing and read the pre-launch report for crashes and web error pages.
- Complete App content: sign-in details for reviewers that stay valid, content rating, target audience, privacy policy and Data safety.
- Start the closed test with 15 or more testers, so one dropout doesn't break the count, and log their feedback.
- Fix what testers report – in Base44, and in a new build with a higher
versionCodewhen the shell changes. - After 14 days, apply for production access with specific answers, then roll out in stages.
appsubmitter.io runs this side for you: Play Console setup, upload key and Play App Signing, CI/CD for the AAB, store listing, Data safety, the closed test plan, your production access answers and the communication with Google's review team – always in your own account. Code changes are quoted upfront. Book the Android service or check your Base44 app with us in a free consultation call. For the iPhone version, see converting Base44 to iOS; Base44 and Guideline 5.6 explains why release discipline matters on Apple's side.
Checklist before you submit
- Your Play Console account is verified, and for a new personal account the 12-tester closed test is planned.
- You chose a route: Base44's AAB, a WebViewGold project with your own package name, or a TWA with a working Digital Asset Links file.
- The bundle you upload targets API level 36.
- Google sign-in works end to end: SHA-256 added in Base44, or Custom Tabs or native sign-in in your wrapper with the session arriving in the app.
- Notification permission, back gesture, file uploads and edge-to-edge layout were tested on Android 16.
- Developer name, contact email and store website match the domain your app loads.
- Data safety covers what your Base44 web content, push service and SDKs collect.
- Account deletion works inside the app, and a public deletion page is linked in the Data safety form.
- Digital goods use Google Play Billing; Stripe or Base44 Payments only cover physical goods and services.
- Reviewer sign-in details are entered under App content and stay valid.
Frequently asked questions
Can I publish a Base44 app on the Google Play Store?
Do I need Android Studio to convert Base44 to an Android app?
Can I use a TWA instead of a WebView for my Base44 app?
Why does Google login fail in my Base44 Android app?
How long does Google Play review take?
Will WebViewGold get my Base44 app approved on Google Play?
Recommended solution
From Base44 to Google Play: 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 – Connecting a domain to your app
- Play Console Help – App testing requirements for new personal developer accounts
- Play Console Help – Target API level requirements for Google Play apps
- Google Play Policy Center – Spam (Webviews and Affiliate Spam)
- Play Console Help – Understanding Google Play's app account deletion requirements
- Android Developers – Trusted Web Activities
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.