Deploy & App Stores
How to Publish a Base44 App on the Google Play Store
You can publish a Base44 app on Google Play by wrapping either the exported frontend (with Capacitor) or the hosted app (with a WebView shell) into an Android project, building a signed .aab and releasing it via Play Console. Expect to run a 14-day closed test with 12 testers if you use a new personal developer account, and to describe Base44's managed backend accurately in the Data safety form.
Which Android approach fits a Base44 app?
For most Base44 apps a WebView or Trusted Web Activity approach around the hosted app is fastest, while Capacitor with exported code gives you more control. The deciding factor is whether your Base44 plan lets you export the code and how much offline or device functionality you need.
Google Play is generally more tolerant of web-based apps than Apple, but its spam and minimum functionality policies still reject apps that add no value over a website.
- Trusted Web Activity: full-screen Chrome rendering, requires a solid PWA and Digital Asset Links
- WebView wrapper such as WebViewGold: configurable native features, no code
- Capacitor with exported code: native plugins, bundled assets, more engineering
How do you set up the Play Console account?
Register a developer account, verify your identity and choose personal or organization carefully. Organization accounts need a D-U-N-S number but avoid the closed-testing rule that applies to new personal accounts.
Create the app in Play Console with a package name you will keep forever, then work through the app content declarations before your first release.
- Pay the 25 USD one-time registration fee and complete verification
- Create the app, choose free or paid and confirm the declarations
- Set up Play App Signing on the first upload
- Fill in app content: privacy policy, app access, ads, content rating, target audience, Data safety
How do you build the Android App Bundle?
Open the generated Android project in Android Studio and create a signed release bundle. Google Play accepts new apps only as .aab files.
Your targetSdk must meet Google's current target API level requirement, which moves up roughly every year, so check it on each release rather than once.
- Upload keystore created once and backed up securely
- versionCode incremented for every upload
- INTERNET permission plus only the permissions you actually use, such as camera for uploads
- Release build tested on at least one older and one current Android version
How does the 12 testers, 14 days closed test work?
Personal accounts created after late 2023 must keep at least 12 opted-in testers in a closed test for 14 consecutive days before requesting production access. Base44 apps are often internal tools or niche products, so recruiting 12 real Android users can take longer than expected; start early.
Google asks about your testing when you apply for production, so collect genuine feedback and ship fixes during the test rather than just waiting out the clock.
- Upload to internal testing and verify login against Base44
- Create a closed track and invite testers via email list or Google Group
- Make sure each tester opts in and installs from the Play Store link
- Release at least one improved build during the 14 days
- Apply for production access with a short summary of what you learned
How do you make a Base44 app behave like a real Android app?
Handle the back button, file uploads and external links correctly; these three cause most bad reviews for wrapped Base44 apps. The back gesture should navigate within the app, uploads should open the native picker or camera, and links to other sites should open in the browser.
Push notifications via Firebase Cloud Messaging are the most valuable native addition, for example to alert users when a record in Base44 changes. You can trigger them from a Base44 backend function or an automation calling your push service.
- Pull-to-refresh and a friendly offline screen
- Correct status bar color matching your Base44 theme
- Login sessions that survive closing the app
How do you complete Data safety for Base44's backend?
Declare the data your app collects even though Base44 stores it, because you are the data controller in Google's eyes. Typical entries are name, email, user IDs and any user-generated content; add location, photos or files if your app uses them.
Google requires an in-app path to request account deletion and a web URL for deletion requests. Build both on top of your Base44 data model before submitting.
- State whether data is encrypted in transit (HTTPS) and whether users can request deletion
- Include third-party SDKs such as analytics or push providers
- Keep the privacy policy consistent with the form
What should you do next?
Start with the closed test as soon as a stable build exists, and polish the listing in parallel. If you want experienced help, neooutput's AI Code Engineers take Base44 apps through Android build and Play Console, and appsubmitter.io supports teams with the submission process.
Frequently asked questions
Can a Base44 app be a Trusted Web Activity?
Yes, if the hosted app meets PWA criteria and you can host a Digital Asset Links file on its domain. With a custom domain this is usually possible; on a default platform subdomain you may not control that file.
Do I need to export code for Google Play?
No. A WebView wrapper around the hosted Base44 app is enough for Play, as long as the app adds value and complies with policies.
Does Google Play require in-app account deletion?
Yes. Apps that allow account creation must let users request deletion in the app and via a web link declared in Data safety.
Can I publish the iOS and Android versions at the same time?
Yes, and it is common. Just note that the Android timeline may be longer if you need the 14-day closed test.
