# How to Publish an App on Google Play: Testing, Review and Launch

> How to publish an app on Google Play: the 25 USD account, the 12 tester closed test, target API rules, store listing, fees, review time and launch.

- Canonical: https://zeroraised.com/blog/how-to-publish-an-app-on-google-play
- Published: 2026-10-21
- Updated: 2026-10-21
- Author: Jay Mokashi (https://zeroraised.com/blog/authors/jaymokashi)
- Publisher: ZeroRaised (https://zeroraised.com/)
- Section: Growth
- Tags: indie-apps, marketplaces, app-launch, product-launch

How to publish an app on Google Play, in short: pay [the 25 USD fee for a Play Console developer account](https://zeroraised.com/launch-sites/google-play), verify your identity and an Android device, upload a signed Android App Bundle that targets API level 36, fill in the store listing and App content forms, then pass a 14 day closed test with 12 testers if you have a new personal account. Apply for production access, send the release for review and launch once it is live. Since 30 September 2026, every app on a certified Android device in four countries must also be registered to a verified developer, which Play handles for most apps automatically.

**Disclosure:** ZeroRaised publishes this guide and appears in the final section. The rules below follow Google's linked Play Console Help and Android Developers documentation as checked on 18 Oct 2026, and this guide makes no promise of installs, rankings, traffic or revenue from Google Play or any launch site.

## TL;DR

The upload is quick. The calendar is not. A new personal account has three waits stacked in a row: the closed test (at least 14 days), Google's review of your application for production access, and the review of the first production release. Start the test as early as you can, and do not announce a launch date until the release is approved.

Three things changed on or around 30 September 2026: developer verification checks began in four countries, the deadline passed for registering Play apps in Play Console, and Google's new service fee table reached Australia and Japan.

| Stage | Where | Google's rule | Common snag |
|---|---|---|---|
| Account | Play Console sign-up | US$25 one-time fee; 18 or older | Prepaid cards are not accepted |
| Identity | Play Console | Legal name, address, contact details; D-U-N-S for organisations | Organisation details must match your Dun & Bradstreet profile |
| Device check | Play Console mobile app | Access to a real Android device (new personal accounts) | Needed before the app can go live |
| Build | Android Studio | App Bundle; target API level 36 since 31 Aug 2026 | A lower target cannot be submitted |
| App content | Play Console | Privacy policy, Data safety, content rating, target audience | Apps that collect no data still need the form |
| Closed test | Testing track | 12 testers, opted in for 14 days in a row (new personal accounts) | Testers who leave reset your count |
| Production access | Dashboard | Short application on your test | Review usually takes seven days or less |
| Release review | Publishing overview | Up to seven days for some new accounts | Managed publishing is off limits for the first release |
| Verification | Play Console verification page | Package names registered to a verified developer | A lost signing key blocks registration |

## What changed on 30 September 2026

Google's [Android developer verification page](https://developer.android.com/developer-verification) (checked 18 Oct 2026) carries a plain heading: "Effective September 30, 2026". Its timeline gives the detail: "Protections begin for all users who install apps from participating stores in Brazil, Indonesia, Singapore, and Thailand on certified devices running Android 7+." The same page says Google will continue rolling out user protections globally in 2027.

The [verification guide](https://developer.android.com/developer-verification/guides) says "Android requires all apps to be registered by verified developers for users to install them on certified" devices. For a maker on Google Play, the useful line is this one: "You will automatically be registered if you distribute your app through Google Play." Play Console is where you check that, and where you register anything Play missed.

That is the second date. Google's [Play policy deadlines table](https://support.google.com/googleplay/android-developer/table/12921780?hl=en) lists 2026-09-30 against Play Console Requirements: "you must register your Play apps in Play Console." It notes that "99% of apps on Play have been registered automatically" and asks developers to check the Play Console Home page and register any remaining apps "to avoid global removal from Google Play".

The third change is about money. Google's [service fees page](https://support.google.com/googleplay/android-developer/answer/112622?hl=en) now splits fees by whether a user's install is new or existing, with the regional rollout date as the cut-off: "June 30, 2026 for the EEA, UK, and US; September 30, 2026 for Australia and Japan". A new app launched today counts every user as a new install, so the new table is the one that applies to you in those markets. The pricing section below has the numbers.

What this means for someone publishing a first app this month:

- **Nothing extra if you stay on Google Play,** as long as Play registers your package name. Google's [verification FAQ](https://developer.android.com/developer-verification/guides/faq) says apps that use Play App Signing are part of the automatic registration process.
- **Keep your signing key safe.** The same FAQ warns: "If you lose your signing key you won't be able to register your packages."
- **Side channels count too.** If you also hand out APKs from your own website, register those package names through Play Console as well. The FAQ says developers with a Play Console account can use it as "the single place to manage all their verification requirements".

None of this changes the 25 USD account, the testing rule or the review queue. It does make a verified Play account the baseline for Android distribution, not an extra.

## How to publish an app on Google Play, step by step

This is the order that keeps the waits from stacking up. Start the account and the closed test early, and build the listing while the test clock runs.

**1. Create a Play Console developer account.** Google's [getting started page](https://support.google.com/googleplay/android-developer/answer/6112435?hl=en) sets the basics: "You must be at least 18 years of age to sign up for a Play Console account", you accept the Developer Distribution Agreement, and "There is a US$25 one-time registration fee". Prepaid cards are not accepted. You may be asked for "a valid government ID and a credit card, both under your legal name", and if that information is found invalid, "your registration fee will not be refunded."

**2. Pick the account type and verify your identity.** Personal or organisation is the one decision that is hard to undo later; the next section compares them.

**3. Verify an Android device (new personal accounts).** The same getting started page says developers with new personal accounts must "verify that they have access to an Android device using the Play Console mobile app before they can make their app available on Google Play." Keep a real phone you can sign in on to hand.

**4. Create the app and upload a first build to internal testing.** Internal testing has no entry requirement. Google's [testing requirements article](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) says builds there are "normally available to testers within seconds of being added in Play Console", and you can start it before your app setup is complete.

**5. Complete app setup:** store listing, privacy policy, Data safety, content rating and target audience. Google requires app setup to be complete before the app can go public, so finish it while the test runs.

**6. Run the closed test** (new personal accounts): 12 testers, 14 days, no gaps.

**7. Apply for production access** from the Dashboard, with three short sections on your test, your app and your readiness.

**8. Set prices and countries, create the production release and send it for review.**

**9. Check registration and launch.** Confirm the app shows as registered on the Android developer verification page in Play Console, then tell people.

If you searched for how to publish an Android app for free, step 1 is the only fixed cost on this path. Everything else is time.

## Personal or organisation developer account

Google's [account type article](https://support.google.com/googleplay/android-developer/answer/13634885?hl=en) says the two types "have access to the same functionality" and can both earn money. The difference is who you are and what checks you face.

The personal account is described as being for "a student, hobbyist, or amateur developer", while an organisation account is for "commercial, industrial, professional, or governmental activities." Google adds that with a personal account "You can still earn money on Google Play and invite others to join your account." An organisation account needs a D-U-N-S number. Google notes that "Applying for a D-U-N-S number through Dun & Bradstreet is a completely free process" and warns about third parties who charge for it.

Some categories have no choice. Google's [Play Console Requirements policy](https://support.google.com/googleplay/android-developer/answer/10788890?hl=en) says developers of financial products, health apps, apps approved to use the VpnService class and government apps "must register as an organization". If you are building a budgeting tool or a symptom tracker, check this before you pay the fee.

| | Personal account | Organisation account |
|---|---|---|
| Who it is for | Individuals, students, hobbyists, solo makers | Companies and other legal entities |
| Identity checks | Legal name, address, contact details | Same, plus a D-U-N-S number matching your Dun & Bradstreet profile |
| Device verification | Required for new accounts | Not described for organisations |
| Closed test before production | 12 testers for 14 days if created after 13 Nov 2023 | Not part of the personal account testing rule |
| Required for | Nothing in particular | Financial, health, VPN and government apps |

The closed test rule is the main practical difference for a solo maker. If you already have a company and its D-U-N-S number, the organisation route skips 14 days of waiting.

## The closed test: 12 testers for 14 days

This is the step most first-time Android makers did not expect. The [testing requirements article](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) is exact: "Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days." Until you meet it, the Production track and pre-registration stay disabled.

Read the wording twice. The count is checked when you apply: "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days." Recruit fifteen or twenty so a few departures do not reset the clock, and tell every tester the rule. Google's own advice is to "Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days."

Where do testers come from? Google suggests friends, family, colleagues and "communities where potential users exist". For a bootstrapped maker the best source is a list you already have. If you are still building one, the guide on [how to build a waitlist before launch](https://zeroraised.com/blog/how-to-build-a-waitlist-before-launch) covers the sign-up side, and [how to get your first 100 users](https://zeroraised.com/blog/how-to-get-your-first-100-users) has ideas for finding the first dozen people who care.

When you apply, you answer questions about recruiting, whether testers "used all available app features", the feedback and what you changed. Google says "You must summarize your testing feedback when applying for production access", so collect it as you go.

After you apply, "Review usually takes seven days or less, but can occasionally take longer." If Google wants more, the reasons it gives include "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period." A test that looks like twelve idle accounts is the likeliest way to lose another fortnight.

## Build requirements: App Bundle, target API level and signing

Three technical rules decide whether Play Console will accept your upload at all.

**Android App Bundle.** The [App Bundle guide](https://developer.android.com/guide/app-bundle) says "From August 2021, new apps are required to publish with the" Android App Bundle on Google Play. Build a signed `.aab` from Android Studio or your CI, not an APK. As the guide puts it, "Google Play uses your app bundle to generate and serve optimized APKs" for each device configuration.

**Target API level.** Google's [target API level article](https://support.google.com/googleplay/android-developer/answer/11926878?hl=en) is the rule that catches people using old templates or tutorials. "Starting August 31, 2026", "New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play", with lower floors for Wear OS, Android Automotive OS, TV and XR apps. Developers can request an extension to 1 November 2026. Set `targetSdk` to 36 or later and check it in any framework's generated Android project, where older defaults hide.

**Signing.** Google's [Play App Signing article](https://support.google.com/googleplay/android-developer/answer/9842756?hl=en) separates two keys. You sign each bundle with an upload key, and Google signs what users download with the app signing key. If the upload key is compromised or lost, "Google can reset this key for you", but an app signing key you manage yourself "cannot be reset if you manage it yourself (without Play App Signing) and lose it." Let Google hold the app signing key, and keep the upload key and its password in a password manager and a backup.

## Store listing and the App content forms

The store listing is your launch page inside Google Play, and the App content section is where Google decides whether the app can be published at all. Both have to be complete before the app can be made publicly available.

Google's [store listing guide](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en) sets the text limits, and calls the short description "The first text users see when looking at your app's detail page on the Google Play app". It also warns that repetitive or irrelevant keywords in the name or description can get an app suspended. The [graphic assets guide](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) covers the images:

| Asset | Google's spec | Required? | What to put there |
|---|---|---|---|
| App name | 30 characters | Yes | The name, plus the job it does if there is room |
| Short description | 80 characters | Yes | The main use in one line |
| Full description | 4,000 characters | Yes | What it does, who it is for, what it costs |
| App icon | 512px by 512px, up to 1024KB | Yes | A higher resolution version of your launcher icon |
| Feature graphic | 1024px by 500px | Yes | A simple brand image that does not repeat the icon |
| Screenshots | Up to 8 per device type; 1,080 to 7,680px for large screens | Add them for each device type you support | The real interface, with little extra text |
| Preview video | Added in the Graphics section | Optional | The core action in the first seconds |

On screenshots, Google's guidance for large screens is to "Exclude additional text that is not part of your core app experience, as this can get cut off on Play homepages on certain screen sizes". If you are recording a preview video, the guide on [how to make a product demo video](https://zeroraised.com/blog/how-to-make-a-product-demo-video) covers scripting a short one.

Then the App content forms, which most first-time makers rush:

- **Privacy policy and Data safety.** Google's [Data safety article](https://support.google.com/googleplay/android-developer/answer/10787469?hl=en) says "All developers must declare how they collect and handle user data", and that includes data collected "through any third-party libraries or SDKs used in their apps." The crash reporter and analytics SDK you added on a weekend count. And no, you cannot skip it: "Even developers with apps that do not collect any user data must complete this form and provide a link to their privacy policy."
- **Content rating.** Google's [content rating article](https://support.google.com/googleplay/android-developer/answer/9898843?hl=en) says you must complete the questionnaire for each new app, and "Apps without a content rating will be removed from the Play Store." Answer it honestly; misrepresentation can lead to removal or suspension.
- **Target audience.** The Play Console Requirements policy reminds developers that if the app's target audience includes children, the Families policy applies. Selecting a wide age range to look friendly brings obligations you may not want.
- **Reviewer access.** The Play Console Requirements policy asks for "an active demo account, login information, and all other resources needed for Google Play to review your app". If your app has a login, create a test account with content in it and put the details in App access.

Before you apply for production access, the testing requirements article lists common problem areas to check, including "Functional reliability" and working test credentials. Stable, honest and testable is the bar.

## Pricing and Google Play's service fees

Decide on the business model before the first release, because one choice is final. Google's [pricing article](https://support.google.com/googleplay/android-developer/answer/6334373?hl=en) says: "Once your app has been offered for free, the app can't be changed to paid. If you want to charge for the app, you need to create a new app with a new package name and set a price." One way around it is to stay free to download and sell a subscription or one-time purchase inside the app through Google Play's billing system. The same article lists setting up a payments profile as the first step for a paid app.

Then the fees. Google's [service fees page](https://support.google.com/googleplay/android-developer/answer/112622?hl=en) says "97% of developers distribute their apps and take advantage of all Google Play has to offer at no charge". If you sell digital goods, the rate depends on where your users are. For users in Australia, the EEA, Japan, the UK and the US, the new table applies:

| Transaction (users in AU, EEA, JP, UK, US) | Auto-renewing subscriptions | Other transactions, new installs | Other transactions, existing installs |
|---|---|---|---|
| First 1 million USD of annual earnings | 10% plus 5% billing fee | 10% plus 5% billing fee | 10% plus 5% billing fee |
| Standard | 10% plus 5% billing fee | 20% plus 5% billing fee | 25% plus 5% billing fee, or 20% for external web links |
| Games Level Up or Apps Experience programs | 10% plus 5% billing fee | 15% plus 5% billing fee | 20% plus 5% billing fee, or 15% for external web links |

The billing fee applies when a user buys through Google Play Billing or makes the initial purchase of a paid app. In all other markets, until the new fees roll out globally, the older structure applies: 15% on the first 1 million USD each year for developers enrolled in the 15% tier, 30% above that, and 15% on auto-renewing subscriptions.

Google's [15% tier article](https://support.google.com/googleplay/android-developer/answer/10632485?hl=en) describes enrolment for the 15% tier in other markets: you must create an Account Group, tell Google whether you have any Associated Developer Accounts and accept the terms for the tier. Do it the week you create the account, not the week of your first sale.

In those five markets, a subscription sold through Play Billing costs 15% in total under the new table, and so does a one-time purchase within your first million in a year.

## Review times and your first production release

Once production access is approved, create a release on the Production track, choose countries and send the changes for review from the Publishing overview page. Google's [publishing status article](https://support.google.com/googleplay/android-developer/answer/9859751?hl=en) is direct about new accounts: "For certain developer accounts, we'll take more time to thoroughly review your app to help better protect users. This may result in review times of up to seven days or longer in exceptional cases."

There is a catch for launch planning. Managed publishing, the switch that holds an approved update until you press publish, is the tool you would want for a launch day. But Google's [managed publishing article](https://support.google.com/googleplay/android-developer/answer/9859654?hl=en) says your app must already be available on Google Play before you can turn it on: "You can't use it when publishing an app for the first time." Without it, changes "will be published automatically as soon as they're reviewed and approved by Google". Your first public release goes live when review finishes, not when you choose.

Google's own planning advice is in the same article: "We recommend that you adjust your planning to include a buffer period of at least a week between submitting your app and going live." For a first launch, that means two practical rules:

1. **Do not announce a date until the app is live.** Wait for the Published status, check the listing on a phone, then pick launch day.
2. **Treat the first public release as a soft launch.** Fix what the first real users find, then use managed publishing for the update you announce.

If a first release is rejected, the status shows as "App rejected", which "only applies to apps in Draft that you're attempting to publish for the first time". You can fix the issue and resubmit, or appeal. Changes made after a rejection are not sent for review automatically; press Send for review again.

After launch, write clear release notes for each version; the guide on [how to write release notes](https://zeroraised.com/blog/how-to-write-release-notes) applies to the "What's new" text on Google Play as much as to a changelog.

## The launch outside the store

Approval puts the app in the catalogue. It does not tell anyone it exists. As editorial judgement rather than a measured rule, the first users of a new app usually come from places where you already have some attention.

A simple launch plan for a solo Android maker:

1. **Before review.** Turn your closed testers into your first reviewers. They already know the app, and they are the people most likely to leave an honest rating once it is public.
2. **Launch day.** Post where your users already are. For Product Hunt, read [how to launch on Product Hunt](https://zeroraised.com/blog/how-to-launch-on-product-hunt) and the [Product Hunt venue page](https://zeroraised.com/launch-sites/product-hunt), and use the [launch time tool](https://zeroraised.com/tools/launch-time) to pick an hour.
3. **The following weeks.** Spread out further listings rather than firing them all at once. The [launch sites directory](https://zeroraised.com/launch-sites) lists venues by audience, and the [product launch checklist for bootstrapped makers](https://zeroraised.com/blog/product-launch-checklist-for-bootstrapped-makers) covers the parts that are not store specific.

## Where a launch listing fits once your app is on Google Play

A published app gives you real launch material: a Play Store link that works, screenshots, a price, a Data safety section anyone can read and a verified developer name. None of that guarantees anyone turns up, and no launch site can promise installs.

[ZeroRaised](https://zeroraised.com/) is a free launch site for bootstrapped makers whose products have no institutional VC or accelerator equity. If your Android app is live on Google Play and fits, you can [submit it for review](https://zeroraised.com/submit), ideally once the store link works rather than while the closed test is still running. The [maker perks page](https://zeroraised.com/perks) is a separate resource for eligible makers. Neither replaces a clear store listing or a fast reply to the first one-star review.

So, how to publish an app on Google Play: pay the 25 USD fee, verify who you are, build an App Bundle that targets API level 36, fill in the listing and the App content forms honestly, run a real 14 day closed test with at least 12 testers, apply for production access and send the first release for review. Since 30 September 2026, check that your package names are registered too. Then let the first release go live quietly, and pick launch day once people can actually install the app.

## Frequently asked questions

### How much does it cost to publish an app on Google Play?

Google charges a one-time US$25 registration fee for a Play Console developer account. Publishing a free app costs nothing beyond that. If you sell the app or digital goods inside it, Google Play takes a service fee; in the UK, US, EEA, Australia and Japan, Google's new fee table charges 10% plus a 5% billing fee on the first 1 million USD of annual earnings according to Google's service fees page.

### Can I publish an app on Google Play for free?

Not entirely. The developer account has a one-time US$25 fee, with no annual renewal. After that, free apps with no paid features carry no service fee. Google's separate Android Developer Console for apps distributed only outside Google Play offers a no-cost limited distribution account for up to 20 devices, but that is not a route onto the Play Store.

### How long does it take to publish an app on Google Play?

For a new personal account, add at least 14 days for the required closed test, then up to about a week for Google to review your production access application, then the review of the release itself. Google says new developer accounts may see review times of up to seven days or longer in exceptional cases, and recommends a buffer of at least a week between submitting and going live.

### Do I need 12 testers to publish on Google Play?

Only if you have a personal developer account created after 13 November 2023. Those accounts must run a closed test with at least 12 testers who stay opted in continuously for at least 14 days before applying for production access. Organisation accounts are not covered by that article's requirement.

### What is Android developer verification and do Google Play developers need to do anything?

It is Google's programme linking apps to verified developers. From 30 September 2026, certified devices in Brazil, Indonesia, Singapore and Thailand check that apps from participating stores come from registered, verified developers, with a global rollout planned for 2027. Developers who distribute through Google Play are registered automatically, but you should check the verification page in Play Console and register any app that is missing.