burgndy.ai
← All articles

September 21, 2026 · 6 min read

How to Publish an Android App to Google Play Without Coding

Publish Android appGoogle Play ConsoleBurgundy AINo-code

How do you publish an Android app to Google Play without coding?

Create a Google Play Console developer account, get a signed Android App Bundle (.aab) from an app builder, prepare a store listing with real screenshots, then release it. If your personal account was created after 13 November 2023, you must first run a closed test with at least 12 testers for 14 days before applying for production access.

Step 1: Create your Google Play Console account

Registration is a one-time $25 fee and can be done from any browser. Decide between a personal and an organization account now: the closed-testing requirement below applies to personal accounts created after 13 November 2023 and does not apply to organization accounts.

Step 2: Get a signed Android App Bundle

Google Play accepts an Android App Bundle (.aab). You don't need Android Studio if a builder compiles and signs it for you — Burgndy.ai produces both an .apk for direct testing and an .aab for Play from a plain-English description.

Step 3: Test it before anyone else does

Install the build on an emulator or a real phone and walk through sign-up and the core flow. Fix what breaks now, because every change you ship later has to go back through review.

Step 4: Prepare the store listing

  • Title: up to 30 characters.
  • Short description: up to 80 characters.
  • Full description: up to 4,000 characters. Our free store listing checker at burgndy.ai/tools/store-listing-checker counts these for you.
  • Screenshots: capture them from the running app. Store guidelines prohibit fabricated listing images.

Step 5: Run the closed test if it applies

For a personal account created after 13 November 2023, Google requires a closed test with at least 12 testers who stay opted in for 14 continuous days before you can apply for production access. Google also checks that testers genuinely used the app: they must be distinct Google accounts installing on real devices, and emulators, bots and duplicate accounts do not count. Organization accounts and older personal accounts are exempt.

Step 6: Apply for production access and release

When the testing requirement is met, apply for production access in the Play Console, then roll out your release. Tip: start recruiting testers while you build, since the 14-day clock is the slowest part of the whole process.

What a builder does and doesn't do here

A tool like Burgndy.ai can compile the .aab, run it on an emulator, and capture real screenshots. It cannot create your Play Console account, recruit your 12 testers, or press the release button for you — those stay with the publisher.