Skip to content
LPR Studio
FREN
Contact us

Mobile appsMethodTimelines

How to publish an Android app on Google Play in 2026

8 min read

Publishing an Android app on Google Play in 2026 takes a developer account (a one-time 25 US dollar fee), an Android App Bundle that targets API level 36, a complete store listing with its Data safety form and, for a recent personal account, a 14-day closed test with at least 12 testers. Budget two to three weeks before the app is public.

We have just been through it with Tubissime, our own personalised song app, which was already on sale on the App Store. This guide follows that release and points out where the official checklist stays quiet.

Pick the right account before anything else

The account type decides your timeline more than your code does.

  • Personal account. Quick to open, but if it was created after 13 November 2023, Google requires a closed test with at least 12 testers who have stayed opted in for the last 14 days in a row before you can apply for production. Lose a tester on day ten and the count starts again.
  • Organisation account. No closed-test requirement, and the listing shows your company as the developer, which is what a business app should do. Google verifies the organisation through a D-U-N-S number, so request it early.

The 25 dollar fee is paid once, against 99 dollars a year for Apple's programme.

Build what Google will accept

An Android App Bundle, signed by Google. New apps are uploaded as AAB files, not APKs. Google builds the per-device packages and signs them with an app signing key it holds; you keep an upload key, which you must guard like a password. In Flutter, flutter build appbundle --release produces the bundle.

A current target API level. Since 31 August 2026, new apps and updates must target Android 16 (API 36). Existing apps that target lower than Android 15 are hidden from new users on newer devices. An app nobody maintains slowly disappears from the store without anyone pressing a button.

Honest declarations. Content rating questionnaire, target audience, and the Data safety form, which must match what the app and every third-party SDK in it actually collect. If users can create an account, Google also requires a way to delete it from inside the app and from the web. Our mobile app requirements template lists these obligations so they land in the brief, not in the last week.

In-app purchases, the part nobody demos

Digital content sold inside an Android app goes through Google Play Billing. Tubissime sells each song as an in-app purchase, with the same three product identifiers as on the App Store, so the server treats both stores alike. Three lessons from wiring it up:

  1. Verify every purchase on your server, through the Google Play Developer API and a Google Cloud service account invited into Play Console. A receipt sent by the phone is never enough to start the work the customer paid for.
  2. Subscribe to real-time developer notifications through a Pub/Sub topic. That is how refunds reach you; without it, a refunded order stays delivered and nobody knows.
  3. Authenticate the push. Any Google account can obtain a valid token for a public endpoint, so check that the message was signed by your own service account and reject everything else.

Android details that cost time

Most of a Flutter codebase carries over from iOS unchanged. These did not:

  • Notification permission. Since Android 13 the app must ask before posting notifications. Tubissime sends at most one local reminder, and only when the user has said yes.
  • Per-app language. Android 13 lets people pick an app's language in the system settings, provided the app declares its languages. All fourteen of Tubissime's languages are listed, and a change applies without restarting the app.
  • Google's test devices open your app. Before release, Google runs the app on its own test devices, and those sessions look like real users. We exclude their published IP ranges from our statistics; otherwise the first numbers after launch are wrong.

Google Play and the App Store side by side

TopicApp StoreGoogle Play
Developer fee99 US dollars a year25 US dollars, once
Testing before launchTestFlight, optional14-day closed test (recent personal accounts)
Upload formatXcode archiveAndroid App Bundle (AAB)
Yearly requirementRecent Xcode SDKRaise the target API level
Paying for digital contentApple in-app purchaseGoogle Play Billing

The Apple half of the same app is in Building an iOS app: from idea to the App Store. For the full budget, store fees and maintenance included, read our guide to mobile app development cost, and to choose the framework, React Native vs Flutter for business apps.

What to put in the quote

If an agency quotes you an Android release, three lines should be explicit: who recruits and follows the 12 testers when the account is personal; how purchases and refunds are verified on the server; and who raises the target API level every year. Each one, left vague, becomes a delay or a bill after launch.

Frequently asked questions

Do I really need 12 testers before my app can go live on Google Play?

Only with a personal developer account created after 13 November 2023. Those accounts must run a closed test with at least 12 testers, opted in continuously for the last 14 days, before Google grants production access. Organisation accounts are exempt, but they must verify the company with a D-U-N-S number, which can take weeks.

What API level must a Google Play app target in 2026?

Since 31 August 2026, new apps and every update must target Android 16, API level 36, to be accepted. Existing apps that target lower than Android 15 stop being offered to new users on newer phones. Raising the target every year is therefore part of maintenance, not an optional upgrade.

How long does a first Google Play release take?

Plan for two to three weeks with a recent personal account, because the mandatory closed test alone lasts at least 14 days. Account verification, the production access request and the review of the first version add a few days on top. An organisation account skips the closed test but has its own verification delay.