Blog Engineering

How to Submit Your App to the Google Play Store

Key takeaways

  • New apps and updates need a signed Android App Bundle that targets Android 16 (API level 36) or higher from August 31, 2026.
  • Personal developer accounts created after November 13, 2023 need a closed test with at least 12 testers opted in for 14 days.
  • Create the app under Home > Create app, then complete the store listing, store settings, pricing and app content declarations.
  • Incorrect app content declarations can delay review or create policy problems, so confirm an answer instead of guessing.
  • Release notes should name the visible changes, such as a fixed crash during onboarding, not a generic line about bug fixes.

Submitting an app to Google Play is not difficult, but it does require preparation. The Play Console asks for product information, store assets, policy declarations, pricing details, and a signed app release before your app can go live.

This checklist covers the Play Console requirements as checked in September 2026; the screenshots show an earlier version of the console. Google updates Play Console requirements over time, so always review the latest Google policy prompts inside your account before submitting a production release.

Before you start

Prepare these items first:

  • A Google Play Console developer account
  • A tested Android app
  • A signed Android App Bundle that targets Android 16 (API level 36) or higher, which new apps and updates need from August 31, 2026 (target API level requirements)
  • A closed test with at least 12 testers opted in for 14 days, if your personal developer account was created after November 13, 2023 (testing requirements for new personal accounts)
  • Store listing copy and visual assets
  • A support email address and website
  • A privacy policy if your app requires one
  • A plan for collecting feedback after launch

Testing matters. Before sending users to the store, run through core flows, crash scenarios, login, payments, and device-specific behavior. If your app already has a beta audience, use in-app bug reporting to collect reproducible reports before the public release.

The Google Play submission steps from this guide: create the app with its name, language, type and price, build the store listing, add store settings, contact details, pricing and availability, complete the app content declarations, upload the signed app bundle with release notes, and review the listing, forms and build before rollout. 1 Create the app Name, language, type, free or paid 2 Store listing Copy, icon, graphic, screenshots 3 Settings and pricing Category, contacts, price, countries 4 App content Rating, audience, data safety, ads 5 Upload the bundle Signed bundle and release notes 6 Review and roll out Check listing, forms and build
The Play Console steps in this guide, grouped into six.

Create your app in Play Console

Log in to the Google Play Console and choose Home > Create app.

You will be asked to define the basics:

  • App name
  • Default language
  • App or game
  • Free or paid
  • Contact email
  • Declarations for the Developer Program Policies, US export laws and Play App Signing terms

Be careful with pricing decisions. Historically, switching a published free app to paid has not been a simple toggle, so make the initial choice deliberately and check the current Play Console rules before launch.

Create app screen in Google Play Console

Build the store listing

The store listing is your app’s public product page. It should explain what the app does, who it is for, and why someone should install it.

In Store presence and Main store listing, prepare:

  • Short description: A concise summary shown near the top of the listing.
  • Full description: A fuller explanation of features, benefits, and use cases.
  • App icon: A clean icon that follows Google’s current asset guidelines.
  • Feature graphic: A wide visual used in parts of the Play Store experience.
  • Screenshots: Phone screenshots, and tablet screenshots if your app supports tablets.
  • Video link: Optional, but useful when the product needs motion or workflow context.

Avoid stuffing keywords into the copy. The listing should be easy to read and accurate to the app experience users will actually get.

Main store listing screen in Google Play Console

Add store settings and contact details

Store settings include your category, tags, contact details, and other discovery information. Choose the category that best reflects what the app does, not the category you wish you were ranking in.

Support contact details matter after launch. If users hit a problem, they need a clear way to reach you. If your team uses Gleap, you can connect app feedback and support workflows with your wider integrations setup so reports reach the right tools.

Set pricing and availability

In the pricing section, choose whether the app is free or paid and where it should be available.

If your app is paid, review tax handling, country-specific pricing, and refund expectations. If your app is free but uses subscriptions or in-app purchases, make sure the listing and policy declarations describe the experience clearly.

App pricing screen in Google Play Console

Complete app content declarations

The app content section is where Play Console asks about content rating, target audience, data safety, ads, privacy, and other policy-sensitive details.

Take this part seriously. Incorrect declarations can delay review or create policy problems later. If you are unsure, pause and confirm the answer instead of guessing.

App content screen in Google Play Console

Upload and release your app bundle

When your listing and app content sections are ready, create a release and upload your signed Android App Bundle. New personal accounts start with a closed testing release and apply for production access from the Dashboard once the testing requirements are met.

You will also need a release name and release notes. Good release notes are short, specific, and customer-friendly. Instead of “Bug fixes and improvements,” explain the visible changes when possible:

  • Fixed a crash during onboarding
  • Improved login error messages
  • Added support for tablet layouts
  • Updated notification settings
App bundle release screen in Google Play Console

Review before rollout

Before clicking rollout, check:

  • The store listing matches the app
  • Screenshots are current
  • App content forms are complete
  • The signed bundle is the intended build
  • Release notes describe the update
  • Support contact details work
  • Your team is ready to monitor feedback

After launch, listen closely. Early reviews, support conversations, and customer feedback surveys can show whether users understand the app, where they get stuck, and which issues should be fixed first.

Publishing is the milestone. Learning from the release is the work that follows.

Frequently asked questions

What do I need before submitting an app to Google Play?

You need a Google Play Console developer account, a tested app, a signed Android App Bundle, store listing assets, contact details, pricing choices, and completed app content declarations.

Can I publish an Android app without testing it first?

You should test the app before submitting it. Google can reject apps that crash, contain broken flows, or do not match the store listing, and early users are likely to leave poor feedback if basic issues slip through.

What assets are needed for a Play Store listing?

A typical listing needs an app name, short description, full description, app icon, feature graphic, screenshots, category, contact details, and optional video. Requirements can change, so always check the Play Console guidance before submitting.

Why are release notes important?

Release notes explain what changed in the submitted version. Clear notes help reviewers, existing users, and support teams understand the update, especially when the release fixes bugs or changes important workflows.

How long does Google Play review take?

Review time varies. Some updates are reviewed quickly, while new apps or policy-sensitive changes can take longer. Submit ahead of your planned launch date so review time does not block your release.

Bug reports with the context to fix them.

7 days free. No credit card needed. 4.6

Book a demo

See Kai answer your own customers' questions, live.

Talk to us

Pricing

Plans, seats and what AI costs, on one page.

See pricing