Base44 Guide
How to publish a Base44 app to Google Play
You built your app in Base44 in an afternoon. Getting it into Google Play is the part nobody warns you about: a developer account, store files, a privacy policy, and above all Google's closed testing requirement — 12 testers enrolled for 14 consecutive days. Here's the complete path.
The publishing path, step by step
Developer account
Create a Google Play Console account (one-time $25 fee). New personal accounts must complete closed testing before publishing.
Store files from Base44
Generate your Android package through Base44's built-in store files feature, including signing and the SHA-256 fingerprint.
Listing and paperwork
Upload to the Console, build your store listing, link a privacy policy, and fill out the Data Safety form accurately.
Closed testing
Run the closed test with 12+ active testers for 14 consecutive days, then request production access.
The blockers Base44 builders hit
"It looks like a website, not an app"
A Base44 app is a web app at heart. If screens aren't mobile-optimized — tiny buttons, horizontal scrolling, clipped text — Google may reject it and testers will say so. Walk through every screen on a real phone before submitting, not just in Base44's preview.
Login works in preview, breaks in the store build
Google sign-in, permissions, and redirects behave differently after packaging and signing. Always test the signed build from the closed testing track on real devices before requesting production.
A generic privacy policy that doesn't match the app
If your app collects emails, stores data, or uses login, your privacy policy and Data Safety form must reflect it precisely. Mismatches are one of the most common rejection reasons.
No 12 real testers
Google requires testers to stay enrolled for 14 consecutive days. A group of friends who install and vanish won't pass, and fake installs endanger your developer account. You need real people with clear instructions — that's exactly what our service provides.
Frequently asked questions
How long does it take to publish a Base44 app?
In most cases 16 to 24 days: a few days of setup and tester recruitment, the mandatory 14-day closed testing window, and a few more days for Google's production review. The 12 testers requirement guide has the full timeline.
Do I need to know how to code?
No. Base44 generates the store files, and the rest is process: forms, a store listing, and a properly run closed test. It's bureaucratic more than technical — but it has to be done right and in the right order.
Where do I find 12 testers?
Recruit in developer communities, use free tester-exchange groups, or use a managed service. We enroll real testers, keep them active for the full window, and deliver a QA report — message us to start.
Related guides: publishing a Lovable app to Google Play and the 12 testers requirement explained.
App ready?
We'll close the 12 testers stage for you.
Built with Base44 and want to reach the store without chasing testers? Send your opt-in link and we run a managed cycle with real testers, clear instructions, and feedback you can act on. Plans from ₪400 (~$120), worldwide.
Start on WhatsApp