What Do You Need Before Publishing an App on the Google Play Store?

To publish an app on Google Play you need a Google developer account (a one-time US$25 fee and identity verification), a signed app bundle that targets Android 16 (API 36) or higher, and the store listing material Google asks for, including a privacy policy. If you open a new personal account, Google also requires a closed test with at least 12 testers for 14 days before you can release to production, so plan roughly two to three weeks before your first public launch.

We build Android, iOS and cross-platform apps, and we publish our own apps on Google Play (MapSeal, Recora, Treasure and Sudoku). This guide is the practical list we would give a business owner before they start. The facts below come from Google's own help pages and developer documentation, which we name as we go. Google changes these rules often, so check the linked pages on the day you publish.

What do you need at a glance?

| Item | What it means |

|---|---|

| Google account | The login you will use for Play Console |

| Registration fee | One-time US$25, per Google |

| Identity verification | Government ID and a credit card, both in your legal name |

| Signed app bundle | Built to the current target API level |

| Privacy policy | A public page describing how your app handles data |

| Store listing assets | Description, icon, screenshots and similar material |

| Content rating questionnaire | Completed in Play Console |

| Data safety form | Completed in Play Console |

Google's account and fee details are on its Play Console Help page. We did not check the last four rows against Google's pages for this article, so confirm them in the Play Console Help articles before you rely on them.

How do you set up a Google Play developer account?

You register for a Play Console developer account with a Google account and pay a one-time US$25 registration fee. This comes from Google's Play Console Help page on creating a developer account.

A few points from that page are easy to miss:

• You must be at least 18.

• Google runs identity checks during setup. You may need a government ID and a credit card, both in your legal name.

• Prepaid cards are not accepted, and the card types that are accepted vary by location.

• If the details you give turn out to be invalid, the fee is not refunded.

The practical advice is to use your real legal details from the start and have your ID and card to hand before you begin. Fixing a rejected registration costs time, and the fee is gone if the details were wrong.

Should you choose a personal or an organization account?

Google lets you choose between a personal and an organization account. If you are a registered business, weigh the organization option seriously. It has its own verification steps and it keeps the app tied to the business rather than to one individual.

Some guides mention a D-U-N-S number for organization accounts. Google's page that we read did not mention one, so check the sign-up screen to see what it asks for in your country.

The choice also affects testing, which is the next section.

What is the testing rule for new personal accounts?

If your personal account was created after 13 November 2023, Google requires a closed test before you can publish to production. According to Google, you need at least 12 testers who stay opted in continuously for at least 14 days. Until you meet that, the Production and Pre-registration options in Play Console stay locked. Once the test is done, you apply for production access from the Play Console dashboard.

New personal accounts also have to confirm they have an Android device, using the Play Console mobile app.

Two things we cannot state as official policy:

• Several third-party guides say organization accounts are exempt from the closed-testing rule. Google's wording does not state this clearly, so confirm it in Play Console before you plan around it.

• Third-party guides also say the 14-day clock restarts if the number of testers drops below 12. Google does not spell that out. Treat it as common experience, and ask your testers to stay opted in for the whole period.

Finding 12 people who will install a test build and stay opted in is the part that catches most first-time publishers out. Start recruiting testers before the app is finished, not after.

What technical requirement must your app meet?

Your app must target a recent Android API level. According to Google's target API level requirements, from 31 August 2026 new apps and app updates must target Android 16 (API 36) or higher.

The requirement differs by device type:

• Wear OS and Android Automotive OS apps need API 35.

• Android TV and Android XR apps need API 34.

• Permanently private apps for internal organization use are exempt.

That date has already passed, so a build made on an older toolchain may be rejected. If you need more time, Google says you can request an extension to 1 November 2026 through Play Console.

There is also a consequence for apps already live. Google says existing apps targeting below API 35 become unavailable to new users on newer Android versions. Third-party sources note that existing users keep the app, and what you lose is the ability to publish updates. If you have an older app, plan the upgrade rather than leaving it.

You will upload a signed app bundle, so make sure your developer or agency builds with a current toolchain and a proper signing setup.

What goes into the store listing?

The listing is what people see before they install, and Play Console will not let you release without the required parts. From our own checklist, you should expect to prepare:

• A privacy policy hosted on a public web page.

• Store listing assets such as a title, description, icon and screenshots.

• The content rating questionnaire.

• The Data safety form, where you declare what data the app collects and how it is used.

We did not verify the exact list of required assets against Google's pages for this article, so read the current Play Console Help articles for each item. The privacy policy and the Data safety form need to match what the app really does. Write them with your developer, because they need to know which SDKs and permissions the app includes.

If your business already has a website, the privacy policy can live there. That is one reason we like to build the website and the app together.

What is developer verification, and does it affect you?

Developer verification is a newer layer on top of the Play account. Google announced in June 2026 that from 30 September 2026, apps installed on certified Android devices must be registered by verified developers. This is described on the Android Developers Blog.

Enforcement starts in Brazil, Indonesia, Singapore and Thailand. Other regions, including India, are planned for 2027 or later, according to Help Net Security's report on the rollout. Google says most Play developers are already verified and that over 99% of their apps are registered.

For most people publishing through Play, the action is simple: check your Play Console home page for your verification status and complete anything it asks for.

How long should you allow?

For a new personal account, allow about two to three weeks for closed testing before the first launch. That is the 14-day test plus time to recruit testers, fix problems and apply for production access. We have not verified Google's review time, so do not build a launch date around a guess. Leave some slack.

If you are building the app from scratch, the app itself takes longer than any of the account steps. The best order is to open the developer account early, because identity checks can take a while, and to start the closed test as soon as you have a stable build.

If you would rather have someone handle the build, the signing, the listing and the release, that is work we do. Tell us what the app needs to do and we will quote it privately.

Frequently asked questions

**How much does it cost to publish on Google Play?**

Google charges a one-time US$25 registration fee for a developer account. If your identity details turn out to be invalid, Google does not refund it.

**Do I need 12 testers to publish my first app?**

If you have a personal account created after 13 November 2023, yes. Google requires a closed test with at least 12 testers opted in continuously for 14 days before production access unlocks. Check in Play Console whether this applies to an organization account, because Google's wording is not clear.

**Which Android version must my app target?**

From 31 August 2026, new apps and updates must target Android 16 (API 36) or higher. Wear OS and Automotive OS apps need API 35, and Android TV and XR apps need API 34.

**Can I use a prepaid card to register?**

No, Google says prepaid cards are not accepted. The accepted card types also vary by location, so check the sign-up screen.

**Does developer verification affect me if I am not in Brazil, Indonesia, Singapore or Thailand?**

Not yet, according to current reports. Google plans other regions, including India, for 2027 or later, so check your Play Console home page for your status.

Sources

• https://support.google.com/googleplay/android-developer/answer/6112435

• https://support.google.com/googleplay/android-developer/answer/14151465

• https://developer.android.com/google/play/requirements/target-sdk

• https://android-developers.googleblog.com/2026/06/android-developer-verification.html

• https://www.helpnetsecurity.com/2026/06/19/android-developer-verification-rollout-markets/