How to publish your Base44 app to Google Play

Published April 2, 2026. Updated November 2, 2026.

Base44 lets you build real apps just by describing them. But once your app is ready, Base44 doesn't handle publishing to Google Play.

That's where this guide comes in.

The gap between "built" and "published"

Building an app and publishing it are two completely different things. Publishing to Google Play requires:

  • Wrapping your app as a native Android app
  • Creating a unique app identity (package name)
  • Designing store screenshots
  • Writing a store description that gets downloads
  • Setting up a privacy policy
  • Building a signed production version (AAB)
  • Submitting to Google for review

That's a lot of steps. But each one can be automated.

The fastest path from Base44 to Google Play

  1. Export your code to GitHub from Base44
  2. Scan it at shippabel.com/scan — see exactly what needs fixing
  3. Click "Make it Google Play ready" — wraps it as a mobile app automatically
  4. Generate your store page — AI writes your name, short description, and full description
  5. Create screenshots — frame them in Android phone mockups
  6. Build and submit — one click to Google Play

Total hands-on time: about 30 minutes. Then you wait for Google's review — usually a few hours to a few days.

Cost breakdown

Google Play Developer account$25 one-time
Shippabel (scan + publish)$99 one-time
Total to go live on Google Play$124

One rule that catches first-time publishers

If you created your Google Play developer account as a personal account after November 2023, Google requires a closed test with at least 12 testers for 14 days before you can release your app publicly. That adds about two weeks to a first launch. Here is how the rule works and how to get through it.

Check your Base44 app for free →