Short answer. Publish the app in Base44, copy its public address (or your custom domain), and paste it into the free APK builder. You get the APK and the AAB for Google Play, both free.
Base44 hosts the front end, the data and the built-in login together, so the published address is the whole app.
Two ways to build it
| Route | Best for | What happens |
|---|---|---|
| Wrap the published address | Every Base44 app | Your data, logins and backend functions stay on Base44; the Android app shows the published app. |
Step by step
Publish and set who can use it
Publish the app in Base44. Check its visibility: if only invited users may sign in, everyone who installs the Android app will see the sign-in screen first, which is right for a team app and wrong for a public one.
Open it on a phone
Load the published address in Chrome on Android, sign in, and go through the main screens. Anything that needs a wide screen needs fixing in Base44 before you build.
Build the app
Paste the address into the APK builder. You get the APK and the Play Store AAB, both free.
What works inside the app
- Base44 sign-in, including Google: the sign-in page opens inside the app and the user comes back signed in.
- Entities, backend functions and integrations, because they run on Base44.
- Photo and file uploads through the phone's picker, and the camera when your app asks for it.
What to check first
Private apps
An app restricted to invited users is fine for staff. For Google Play, Google's reviewers must be able to get in: give them a test account in Play Console.
Your address is your app
Changing the app's subdomain later breaks installed copies. A custom domain avoids that.
Payments
Digital goods and subscriptions inside a Play app need Play Billing: in-app purchases.
Publishing your Base44 app on Google Play
Google Play takes an AAB (Android App Bundle), not an APK. The builder gives you the AAB free with every build, signed with a key that stays the same for the same package name, so keep that package name for every update and raise the version number each time. Before you submit, go through the Play Store checklist: a privacy policy, screenshots, the data-safety form and, for a new personal developer account, the closed test with testers.
If Play reports that the signing key does not match, read fixing the upload key error.
Questions
Do changes in Base44 reach the app?
Yes. The app loads the published site, so publishing in Base44 updates every installed app.
Is it free?
Building the APK is free and needs no account.
Can the app send push notifications?
Yes, when you build with the AppMint app; see AppMint Push.
Other builders
Lovable to APK
You built the app in Lovable and it works in the browser. Here is how to get it onto phones as a real Android app, insta…
Google AI Studio to APK
Google AI Studio can build a working web app from a prompt, but it stops at the browser. AppMint takes the ZIP you downl…
Bolt.new to APK
Bolt.new builds and runs full web apps in the browser. To put one on Android phones you do not need React Native or Expo…
v0 by Vercel to APK
v0 generates Next.js apps and deploys them to Vercel in one click. The deployed app is exactly what you need to build an…
Replit to APK
Replit Agent builds full-stack apps with a real server and database. That server keeps running on Replit; the Android ap…
Bubble to APK
Bubble apps are full web applications with logins, workflows and a database. You can put one on Android by packaging the…
Framer to APK
Framer sites are polished and fast. As an app, a Framer site works best when it gives people a reason to keep it on thei…
Google Sites to APK
Google Sites is how many schools, clubs and small teams publish information. Putting that site in an app gives people on…
All builders
Every app builder we have a guide for, in one list.
Last checked 2026-09-25.