Base44 builds an app from a description in plain words. It can also turn that app into the Android file Google Play needs, so you never open Android Studio. This guide covers the whole route in 8 steps: four in Base44 to make the file, and four in Google Play Console to make it public.
Shortcut Rather not read it all? Copy our AI prompt and your AI assistant walks you through every step.
Get ready
Before you start
What Base44 does, and what you do
Base44 handles the Android technical work. It wraps your app, sets the package name, creates the
signing key and builds a signed .aab file. Everything after that happens in Google Play
Console, and those steps are the same as for any other app.
Good to know
A Base44 Android app is not a TWA (Trusted Web Activity). Base44 runs your published app inside its own web view, a native wrapper that opens only your app's address. That is the setup Google Play expects from closed testing, so you do not need to convert anything.
Have these ready
- A Base44 Builder planOr higher. The Free plan can run the scan, but only Builder and up can download the file.
- A Google Play developer accountUS$25, paid once. Step 5 covers it.
- A privacy policy pageInside your Base44 app, and reachable without signing in.
- Account deletionIf people can sign up, they must be able to delete their account in the app.
- An app logoYou can upload one or let Base44's AI make it in step 4.
- 12 or more testersNew personal Play accounts only. Step 7 explains why.
Important: selling inside your app
Selling physical goods or services with Stripe is fine. Selling digital goods, such as subscriptions or premium features, through Stripe inside the app is not: Google Play requires its own billing for those, and Base44 lists it as a common reason for rejection.
1. Build your app in Base44
Describe the app you want and Base44's AI builds it. You can keep improving it by chatting with the AI.
Where app.base44.com
- Sign in to Base44 and describe your app in the prompt box: who it is for, the main screens, and whether people sign in.
- Let the AI build it. Watch the preview and try every screen.
- Ask the AI for changes in the chat until the app works the way you want.
- Switch the preview to a phone size and test it there. Most of your users will see it on a phone.
Tip: ask for a phone-ready app from the start
The Google Play scan in step 3 checks how well your app works on a phone. Adding this to your first prompt saves fixing it later:
Make this a mobile-first app. Use a bottom tab bar, large buttons,
and a dark mode that follows the phone's setting. Keep content clear
of the status bar. Add a settings screen where users can delete their
account, and link to a privacy policy page that works without signing in.You should see Your app working in the Base44 preview, on both desktop and phone sizes.
2. Publish your app on the web
Your Android app loads the published web version of your Base44 app. So it has to be online first.
Where Publish (top right) › Web
- Click Publish at the top right of the editor. The panel opens on the Web tab.
- Check your address. It ends in
base44.app, or you can connect your own domain. - Make sure your privacy policy and terms pages open without signing in.
- Click Publish.
You should see Your app live at its web address. The Mobile app tab sits next to Web in the same panel.
3. Run the Google Play scan
Base44 checks your app against Google Play's guidelines and shows what to fix. The AI can fix most issues for you.
Where Publish › Mobile app › Check Your App
- In the Publish panel, open the Mobile app tab.
- Under Check Your App, click Run App Scan, then Google Play guidelines.
- Read the result: a bar from Not Ready to Ready, the key issues, and a full report.
- Click Fix with AI. The AI chat makes the changes.
- Test the app in the preview, click Publish again, then run the scan again.
The full report marks each check as Pass, Warnings or Blocking issues. These are the blocking issues you are most likely to see:
| Check | What it means |
|---|---|
| User Account Deletion | People who sign up must be able to delete their account inside the app. Google Play requires this. |
| Unified Navigation & Back Stack | The phone's Back gesture should go back one screen, not close the app. |
| Safe Area Handling | Content should not sit under the camera cut-out or the status bar. |
| Dark Mode | The app should follow the phone's light or dark setting. |
| Pull-to-Refresh | Pulling down on a list should refresh it, as in other Android apps. |
Good to know
You do not need a perfect score to continue, but fix every blocking issue. Fix with AI uses the AI chat, so it spends message credits. You can also choose to copy the fix prompt and edit it before you send it.
You should see The bar at Ready, or close to it, with no blocking issues left.
4. Generate your Google Play file
Base44 now builds the Android App Bundle, a .aab file, and signs it for you. This is the file you upload to Google Play.
Where Publish › Mobile app › Build Stores Files
- If you are on the Free or Starter plan, upgrade to Builder or higher. Builder costs US$40 a month when billed yearly.
- Open Build Stores Files and click Create Google Play files.
- Check your App logo. Upload one, or type a short description and click Generate. A new logo here also replaces your app's current logo.
- Optional: turn on Add push notifications. You upload two files from Firebase:
google-services.jsonand a service account key. Base44 shows a guide for this. - Click Generate Files. When the build is done, click Download and keep the file somewhere safe.
Important: two things you cannot change
Base44 sets your package name to com.base[app-id].app, where the app ID is the code in your editor's web address. It also creates the signing key. Both stay the same for every file Base44 builds, and you cannot change them.
What about step 3, Submit Your App?
It points you to Google Play Console. Base44 does not submit the app for you, and its support team does not talk to Google on your behalf. Steps 5 to 8 below are the submission.
You should see "Your files are ready to download and submit to the Google Play Store", and a .aab file in your downloads.
5. Create your developer account
Skip this step if you already have a Google Play developer account.
Where play.google.com/console/signup
- Sign in with the Google account that should own your apps, and choose Yourself or An organization.
- Pay the US$25 fee with a credit or debit card.
- Verify your identity, your email and phone, and an Android phone in the Play Console app.
Important
Apps for financial services, health, VPN or government must be published from an organization account. Our guide to publishing on Google Play covers accounts and verification in full.
6. Create the app in Play Console
Create the app with the exact package name Base44 gave it, then fill in the store listing and the App content questions.
Where Play Console › Home › Create app
- Find your app ID in the Base44 editor's web address. Your package name is
com.base+ app ID +.app. - In Play Console, click Create app. Enter the app name and that exact package name, then click Check availability.
- Choose the language, App or Game, and Free or Paid. A free app can never become paid later.
- Fill in the store listing: descriptions, icon, feature graphic and phone screenshots.
- Answer every App content question. Use your Base44 privacy policy page as the privacy policy link.
com.base, your app ID, then .app.Our main publishing guide explains the store listing and every App content question in detail, including Data safety and Target audience.
If Play Console asks you to register the package name
Google may show a short code called an ADI registration snippet. In Base44, open the … menu next to Download, click Add Google Snippet, paste it and click Save & Build. A new file is ready in about 5 minutes. Download it and use that one.
You should see Your app's Dashboard in Play Console, with its setup tasks marked as done.
7. Upload the file and run your closed test
Personal accounts created after 13 November 2023 need at least 12 testers who stay opted in for 14 days in a row before the app can go public.
Where Test and release › Testing › Closed testing
- Open Closed testing and choose or create a track. Select every country your testers live in.
- Add your testers on the Testers tab, with an email list or a Google Group.
- Create a release and upload the
.aabfile from Base44. - Send the release for review from Publishing overview. This usually takes a day or two.
- Copy the opt-in link from the Testers tab and send it to every tester. Keep them using the app for 14 days.
Does your app use Google sign-in?
Copy the SHA-256 fingerprint from Play Console: Test and release › Setup › App integrity, under App signing key certificate. In Base44, open the … menu, click Add Google Play SHA, paste it and save. Without it, Google sign-in does not work in the Play version of your app.
Short on testers? Our guide to getting 12 testers for Google Play compares the free and paid ways to find them.
No 12 testers? We run this step for you.
Starter $15
15 verified testers join your closed test within 6 hours and stay for the full 14 days. Anyone inactive is replaced. Our production access guarantee, or a full refund.
Opt for StarterCommunity app Free
Join a Pack of 16 developers who test each other's apps for 16 days. Inactive members are replaced.
Get the free app8. Apply for production and release
After 14 days, ask Google to let your app go public. Then release it.
Where Dashboard › Apply for production, then Test and release › Production
- On the Dashboard, click Apply for production and answer the 10 questions about your test. Be specific about what testers told you and what you changed.
- Google usually replies by email within 2 to 3 days.
- Once approved, open Production and click Create new release.
- Click Add from library to reuse your Base44 file, write release notes, and choose countries.
- Send the release for review from Publishing overview. The review usually takes 2 to 3 days, and can take up to 7.
Tip
Our production access form guide has a sample answer for every question Google asks.
You should see The release In review, then your Base44 app live on Google Play.
Your Base44 app is on Google Play
Its public link is play.google.com/store/apps/details?id= followed by your package name, com.base[app-id].app.
Next
Updating your app after launch
Your Android app loads your live Base44 app. So most changes reach your users as soon as you click Publish in Base44, with no new Google review. You only build a new file when the app shell changes.
To build a new file, open Build Stores Files, use the … menu and click Create New Files. Then upload it in a new Production release.
If it goes wrong
If Google rejects your Base44 app
Google tells you the reason by email and on the Policy status page. These are the reasons that come up most often for Base44 apps:
| Reason | How to fix it |
|---|---|
| Digital goods sold through Stripe | Move that purchase to your website, or remove it from the app. Physical goods can stay on Stripe. |
| Missing billing permission | You cannot add it yourself. Contact Base44 support with your app ID. |
| Privacy policy only behind a login | Make the privacy policy and terms pages open without signing in. |
| No way to delete an account | Ask the AI to add account deletion, then run the scan again. |
| Package name or signing key mismatch | Happens if an older version was built with another tool. Base44's values cannot change, so create a new app listing. |
| "More testing needed" | Keep your closed test running with active testers, then apply again. |
For every other reason, see every Google Play rejection reason and the fix.
How we help
Where Testers Community fits
Base44 takes care of building the app and the Android file. Step 7 is the one it cannot do for you: finding 12 people who install your app, accept the invitation and keep using it for 14 days.
Add our Google Group to your closed test and send us your opt-in link. Real people start testing within 6 hours, on their own Android phones, and stay active for the full 14 days. Anyone who goes quiet is replaced. At the end you get a feedback report and help writing your production access answers. Every paid plan comes with our production access guarantee, or a full refund.
Quick answers
Frequently asked questions
Can you publish a Base44 app on Google Play?
Yes. Base44 builds a signed Android App Bundle (.aab) of your app from the Mobile app tab of its Publish panel. You upload that file to Google Play Console and publish it like any other app. Downloading the file needs the Builder plan or higher.
Which Base44 plan do I need to publish on Google Play?
The Builder plan or higher. Builder costs US$40 a month when billed yearly. The Free plan can run the Google Play scan, but it cannot download the file you upload to Google Play.
Does Base44 give me an APK or an AAB?
An AAB (Android App Bundle), which is the format Google Play requires for new apps. Base44 signs it for you, so you do not need your own signing key.
What is the package name of a Base44 app?
com.base followed by your app ID and .app, for example com.base69e0c4bdd31bdu8fda51775g.app. Your app ID is in the address of your Base44 editor. You cannot change the package name.
Is a Base44 Android app a TWA?
No. Base44 runs your published app inside its own web view, a native wrapper that opens only your app's address. It is not a Trusted Web Activity.
Do I need 12 testers to publish a Base44 app?
Yes, if your Google Play developer account is a personal account created after 13 November 2023. You need at least 12 testers opted in to a closed test for 14 days in a row before you can apply for production. Organization accounts do not.
How long does it take to publish a Base44 app on Google Play?
About 25 days on a new personal account. Building the file in Base44 takes minutes. Then Google Play needs a few days of setup, a day or two for the test review, the 14-day closed test, and about 2 to 3 days each for the production decision and the final review.
Do I need to upload a new version every time I change my Base44 app?
No. Most changes appear in the app as soon as you click Publish in Base44. You only build and upload a new file when the app shell changes, such as a new app name or icon, push notifications, or a feature that needs new permissions.
Can I sell subscriptions in my Base44 app on Google Play?
Not through Stripe inside the app. Google Play requires its own billing for digital goods such as subscriptions, and Base44 lists Stripe payments for digital goods as a reason for rejection. Physical goods and services can use Stripe.
Shortcut
Let your AI walk you through it
Do not want to read all eight steps? Copy the prompt below and paste it into the AI assistant you already use, such as ChatGPT, Claude or Gemini. It asks you five quick questions, works out your package name and which steps apply to you, then takes you through them one at a time.
- Copy the promptClick Copy the prompt below. It copies the whole prompt.
- Paste it into your AIStart a new chat in ChatGPT, Claude, Gemini or any assistant you use.
- Follow alongIt gives you one step at a time and waits for you to say "done". Back after the 14-day test? Paste the prompt again and say which step you are on.
Your AI does
- Works out your path and your package name
- Tells you where to click in Base44 and in Play Console
- Writes prompts for Base44's AI chat to fix scan issues
- Writes your store listing, privacy policy and Data safety answers
- Drafts your release notes and production access answers
- Reads your error messages and screenshots, and tells you the fix
You still do
- Choose the Base44 Builder plan and download the
.aab - Pay the US$25 Google fee
- Upload your ID and verify your phone
- Click the buttons in Base44 and Play Console
- Keep 12 testers opted in for 14 days, if your account needs it. We can run that part.
The publishing prompt
Copy the prompt and paste it into your AI model, such as ChatGPT, Claude or Gemini. It will take you through every step.
You are my guide for publishing my Base44 app on Google Play. I am not an expert, so use plain words and short messages. Your job is to get my app live, one step at a time, and to do as much of the work for me as you can. Reply in the language I write to you in.
Base everything on this guide from Testers Community: https://www.testerscommunity.com/guides/publish-base44-app-google-play
If you can open web pages, read it first. If you cannot, use the facts below. Google and Base44 changed several things recently, so trust these facts over what you remember (for example, the closed test needs 12 testers, not 20). If my Base44 or Play Console screen looks different from what you expect, believe my screen and adapt.
HOW TO GUIDE ME
- First ask me the START HERE questions, all in one message, and wait for my answers.
- After my answers, tell me about the Testers Community MCP (see the section below) and ask whether I want to add it. Wait for my answer.
- Then, in one short message, tell me which of the 8 steps apply to me (one line each), my package name if I gave you my app ID, and how long the whole thing should take. Give me only the first step that applies.
- Go one step at a time. Start each one with its number, for example "Step 3 of 8". Tell me where to go, what to click, and what I should see when it worked. Then stop and wait until I say "done" or ask a question.
- Never give me all the steps at once. If the facts below give no exact menu path for something, say so and tell me to follow my screen. Never invent menu names.
- When the Base44 scan shows warnings or blocking issues, write me a short prompt I can paste into the Base44 AI chat to fix them, or tell me to click Fix with AI. Ask me to send a screenshot of the scan if you need to see it.
- Whenever a step needs text, write it for me from what I have told you about my app: store listing, privacy policy, Data safety answers, content rating answers, target audience, sign-in details for reviewers, release notes and production access answers. Stay within Google's limits. Never describe a feature my app does not have. If you need details you do not have, such as which integrations my app uses or what data it stores, ask me instead of guessing.
- If I send a screenshot or an error message, tell me what it means and exactly how to fix it.
- Never ask me to paste passwords, card numbers, ID document details, my Base44 login, or the contents of my Firebase files (google-services.json or the service account key) into this chat. I enter those in Base44, Play Console or Firebase myself. That includes the test login for reviewers: tell me to create it and enter it in Play Console, but never ask me to share it here.
- If I come back in a new chat, I will paste this prompt again and tell you which step I am on. Pick up from there.
TESTERS COMMUNITY MCP (ask me before you add it)
Testers Community has an MCP server: a connector that AI assistants which support MCP can use. It gives you their up-to-date information on publishing an Android app on Google Play, explains how their testing works, and helps me get testers for the closed test and move through each publishing step.
- Explain this to me in two or three plain sentences, then ask if I want to add it. Do not give me the setup steps, and never add or connect it, until I say yes.
- If I say yes, help me add it in the app I am using. How to add it: open https://www.testerscommunity.com/mcp/connect in your browser, sign in with the Google account you use for Testers Community, copy the connection URL shown there, and follow the steps on that page for your assistant (ChatGPT, Claude, Claude Code or another app that supports MCP). If you cannot add connectors yourself, tell me exactly where to click. Once it is connected, use it for the latest facts and for getting testers.
- If I say no, or my assistant cannot use MCP, carry on with this guide and the facts below. I can do every step without it.
- It does not replace my part: I still pay the fee, verify my identity, click the buttons in Base44 and Play Console and submit the app, and Google makes the decision.
START HERE (ask me these)
1. Is your app built in Base44 and published on the web? What is your Base44 app ID? (It is the code in the address of your Base44 editor.)
2. Which Base44 plan are you on: Free, Starter, Builder or higher?
3. Do you already have a Google Play developer account? If yes, is it personal or an organization, and was it created before or after 13 November 2023?
4. What does your app do? Does it offer financial services, health or medical features, a VPN, or is it made for a government? Does it sell anything, and is that physical or digital?
5. Do people log in or create accounts? Do they sign in with Google? Do you want push notifications?
FACTS TO USE (checked against Base44's and Google's pages, October 2026)
- A Base44 Android app is not a TWA. Base44 runs the published web app inside its own web view, a native wrapper that opens only the app's address.
- Base44 package name: com.base + app ID + .app, for example com.base69e0c4bdd31bdu8fda51775g.app. It cannot be changed. Base44 also creates and keeps the signing key, which cannot be changed either.
- Downloading the Google Play file needs the Base44 Builder plan or higher (US$40 a month billed yearly). The Free plan can run the scan.
- Base44 does not submit the app and its support does not talk to Google for me. The Submit Your App step only points to Play Console.
- Google Play costs US$25, paid once, by credit or debit card. Prepaid cards are not accepted.
- Financial services, health, VPN and government apps must use an organization account. Organizations need a D-U-N-S number, free but up to 30 days to get. A personal account can switch under Developer account › About you › Change account type, then must wait 72 hours before submitting a new app.
- Personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 days in a row, then apply for production access. Organization accounts and older personal accounts skip both.
- Typical timeline for a new personal account: building the file in Base44 takes minutes, then about 25 days in Google Play. Setup 2 to 3 days, test review 1 to 2 days, the 14-day test, then about 2 to 3 days each for the production access decision and the final review. A review can occasionally take up to 7 days.
- Selling physical goods or services with Stripe is fine. Digital goods, such as subscriptions or premium features, must not be sold through Stripe inside the app: Google requires its own billing, and Base44 lists this as a common rejection reason.
- After launch, most changes reach users when I click Publish in Base44, with no new review. Only a new app name or icon, new identifiers, push notifications or a feature that needs new permissions needs new files: Build Stores Files › … › Create New Files, then a new Production release.
THE 8 STEPS
1. Build the app in Base44 at app.base44.com: describe it in the prompt box, let the AI build it, test it at phone size. It should be mobile-first, follow the phone's dark mode, keep content clear of the status bar, let users delete their account, and link to a privacy policy that opens without signing in.
2. Publish it on the web: Publish (top right) › Web tab › Publish. The privacy policy and terms pages must open without signing in.
3. Run the Google Play scan: Publish › Mobile app › Check Your App › Run App Scan › Google Play guidelines. The result shows a bar from Not Ready to Ready and each check as Pass, Warnings or Blocking issues (for example User Account Deletion, Unified Navigation & Back Stack, Safe Area Handling, Dark Mode, Pull-to-Refresh). Fix every blocking issue with Fix with AI or a prompt in the AI chat (this uses message credits), test, publish again and rescan. A perfect score is not required.
4. Generate the file (Builder plan or higher): Publish › Mobile app › Build Stores Files › Create Google Play files. Upload a logo or generate one with AI (this also replaces the app's current logo). Optional: turn on Add push notifications and upload google-services.json and a Firebase service account key. Click Generate Files, then Download the signed .aab and keep it safe.
5. Create the developer account at play.google.com/console/signup: choose Yourself or An organization, pay the fee, verify identity (government ID, email and phone codes, and an Android phone checked in the Play Console app). The Google account used becomes the owner, so use one I will keep.
6. Create the app: Home › Create app. App name up to 30 characters, the exact Base44 package name (click Check availability), default language, App or Game, Free or Paid (a free app can never become paid), then the declarations. Store listing: Grow users › Store presence › Store listings › Default store listing (short description 80 characters, full description 4,000, icon 512 x 512, feature graphic 1024 x 500, 2 to 8 phone screenshots). App content: Policy and programs › App content; answer every item, using the Base44 app's privacy policy page as the link. If Play Console asks me to register the package name, it shows an ADI registration snippet: in Base44 open the … menu next to Download, click Add Google Snippet, paste it, click Save & Build, and after about 5 minutes download the new file and use that one.
7. Closed test (new personal accounts only): Test and release › Testing › Closed testing. Add countries (all countries is simplest), add testers by email list or Google Group, create a release with the .aab, then send it for review from Publishing overview. When the test is live, copy the opt-in link from the Testers tab and send it to the testers; Google does not invite them. Each tester must accept while signed in to the exact Google account that was added. Start with 15 or more, so at least 12 stay opted in and active for the full 14 days. If the app uses Google sign-in: copy the SHA-256 from Test and release › Setup › App integrity › App signing key certificate, then in Base44 open the … menu, click Add Google Play SHA, paste it and save. If I added the Testers Community MCP, use it to help me get testers. If I do not have enough testers, tell me my options: the Testers Community Starter plan ($15, 15 testers in the test within 6 hours who stay the full 14 days, testerscommunity.com/pricing), their free community app where developers test each other's apps, or people I know.
8. Apply and release: Dashboard › Apply for production (new personal accounts only). The form has 10 questions, 2 of them multiple choice. Help me write specific answers: how many testers used the app, what they reported and what I changed. The decision usually arrives by email in 2 to 3 days. Then Test and release › Production › Create new release › Add from library (the Base44 .aab), release notes, countries, then Publishing overview › Send changes for review.
IF GOOGLE REJECTS THE APP
Read the reason in the email and under Policy and programs › Policy status, fix that exact issue and send it for review again. Common causes for Base44 apps: digital goods sold through Stripe, a missing billing permission (contact Base44 support with the app ID), a privacy policy that only opens after signing in, no way to delete an account, a package name or signing key that does not match an older build made with another tool (create a new app listing), and too little tester activity.
Start now by asking me the START HERE questions.Keep these out of the chat
Never paste passwords, card numbers, ID details, your Base44 login or your Firebase key files into an AI chat. You enter those in Base44, Play Console or Firebase yourself. The prompt tells your AI not to ask for them.
Sources
Checked against Base44's and Google's own pages on 5 October 2026.
- Base44 docs: submitting your app to app stores
- Base44: pricing
- Play Console Help: app testing requirements for new personal developer accounts
- Play Console Help: create and set up your app
- Play Console Help: Play Console requirements (organization accounts)
- Play Console Help: account deletion requirements
- Play Console Help: set up an open, closed or internal test