How to Publish a Base44 App on Google Play
Short answer: To put a Base44 app on Google Play, publish it on a custom domain, package it as an Android App Bundle using a native wrapper such as WebViewGold, and release it through the Play Console with a completed Data safety form, content rating and testing track. Plan the account type early, because new personal developer accounts must pass a closed test before production access.
On this page
Three ways to package a Base44 app for Android
Base44 delivers a hosted web application, so Android needs a packaging layer. You have three realistic options, and the choice depends on how native the app must feel.
- Trusted Web Activity: Chrome renders your site full-screen inside an Android app. Lightweight and good for PWAs that meet Chrome's quality criteria, but limited native integration and dependent on Chrome being available.
- Native WebView wrapper: an Android app built around a WebView with native features such as push, file handling, offline mode and a JavaScript bridge. WebViewGold falls into this category and ships as an Android Studio project.
- Native rebuild: reimplement the app in Kotlin or a cross-platform framework. Maximum control, but you then maintain two products, which defeats the speed advantage of Base44.
Choosing the developer account wisely
Google charges a one-time 25 USD registration fee. The bigger factor is the account type. New personal accounts must run a closed test with a minimum number of opted-in testers for a minimum number of days before applying for production. Google has adjusted these thresholds over time, so check the current requirement in the Play Console help.
Organization accounts require a D-U-N-S number and verification of the business, and they display the company as the developer. Base44 apps are often business tools sold to clients, so an organization account usually fits better and avoids the closed-test wait. Whatever you choose, add a second admin so access is never tied to one person.
Packaging steps with a WebView wrapper
A practical sequence for a Base44 project looks like this.
- Publish the Base44 app on your custom domain and confirm it works on mobile Chrome, including login and all forms.
- In the WebViewGold Android project, set the start URL, package name, app label, adaptive icon and theme colors.
- Decide which domains open inside the app and which open externally; payment providers, help centers and social links often belong outside.
- Configure Android App Links by hosting an assetlinks.json file on your domain, so emailed links like invitations open directly in the app.
- Enable Firebase Cloud Messaging if you want push notifications, and the file chooser and camera permissions if users upload documents or photos.
- Set the target SDK to the level Google currently requires, then build a signed release bundle (.aab) with Play App Signing enabled.
- Install the release build on two or three physical devices from different manufacturers and test the main user journeys.
Need a hand? WebViewGold helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.
Base44-specific issues on Android
Login is the first thing to verify. If your Base44 app offers Google sign-in, remember that Google blocks OAuth inside embedded WebViews; the wrapper should open that step in a Custom Tab or the app should offer an email-based login. Session cookies must persist after the app is closed, otherwise users are logged out constantly, which leads to poor ratings.
Data-heavy screens are the second area. Base44 apps often include tables, filters and dashboards designed on a desktop. On a phone, these need responsive layouts, horizontal scrolling only where unavoidable, and inputs that are not hidden by the keyboard. Adjust them in Base44 itself; the wrapper cannot fix a layout that was never made for small screens. Finally, test the Android back button on every screen with dialogs and multi-step forms.
Completing the Play Console requirements
The Play Console guides you through a set of declarations. For Base44 apps, the Data safety form deserves the most attention: list the data the app collects, such as names, emails, uploaded files and usage data, and what is shared with third parties, including integrations Base44 uses on your behalf. The answers must match your privacy policy.
Also complete the content rating questionnaire, target audience, ads declaration and app access instructions with working test credentials. If users can create accounts, Google requires a way to request account deletion both in the app and through a web link. Upload a feature graphic of 1024 x 500 pixels, phone screenshots and a short description of up to 80 characters that states what the app does in plain words.
Launching and maintaining the Android app
Start with internal testing for your team, then closed testing for a group of real users or clients, then production with a staged rollout. Watch the Android vitals dashboard for crashes and ANRs during the first days. Respond to reviews quickly; early ratings shape how the store presents your app.
After launch, Base44 changes reach users instantly through the web layer, while the Android project needs occasional updates, mainly for new target API requirements and new native features. appsubmitter.io can run these releases and the Console paperwork in your own account, and WebViewGold provides updated templates as Android evolves. A free call helps you decide which parts to keep in-house.
Frequently asked questions
Is a Trusted Web Activity enough for my Base44 app?
It can be, if your app works well as a PWA and you need little native integration. TWAs require verified domain ownership and rely on Chrome. If you need native push handling, file uploads with camera access, offline fallback screens or a JavaScript bridge to device features, a native WebView wrapper is the more flexible choice.
How long does Google Play review take for a Base44 app?
Review times vary from hours to several days, and first submissions or apps from new accounts often take longer. The bigger timeline factor for new personal accounts is the mandatory closed test before production access. Organization accounts with complete verification typically reach production faster.
Do I need to republish the Android app when I change my Base44 app?
No, not for regular changes. The wrapper loads your live Base44 app, so updates appear immediately. You only upload a new bundle when native elements change, such as the icon, permissions, push configuration or target API level. Keep testing key flows on a device after significant Base44 changes.
