The Play Console & Listing

The Google Play Console is the web dashboard where you create your app, upload bundles, write your store listing, manage testers, and roll out releases.

It also handles policy compliance: content rating, data safety, target audience, and the declarations Google requires before going live.

This lesson walks through registering an app, building a great listing, and the forms you must complete to pass review.

In the Play Console you click Create app and provide:

• App name — up to 30 characters, shown on the store.
• Default language.
• Whether it is an app or game, and free or paid.
• Confirmation that you follow Play policies and US export laws.

The app's applicationId (set in Gradle) is permanent once published — choose it carefully, you can never change it.

Your store listing is the page users see before installing. The text fields are:

• App name — 30 chars.
• Short description — 80 chars, shown first and very important for conversion.
• Full description — up to 4000 chars, explains features and benefits.

Write for humans, not just keywords. The short description is what convinces a browsing user to tap.

Play requires several images, each with strict sizes:

• App icon — 512×512 PNG, 32-bit.
• Feature graphic — 1024×500, shown at the top of the listing.
• Screenshots — at least 2 per form factor (phone), up to 8; recommended for tablets too.

Screenshots are your most persuasive asset. Use captions to highlight what each screen does.

You must complete the content rating questionnaire (run by the IARC). You answer questions about violence, language, user interaction, gambling and so on.

Based on your answers, Play assigns regional ratings (ESRB, PEGI, etc.). Answer honestly — a mismatch between your rating and actual content can get the app suspended.

Without a completed rating, you cannot publish to production.

The Data safety form is mandatory. You declare what data your app collects and shares, why, and whether it is encrypted in transit.

Categories include location, contacts, financial info, identifiers and more. This information is surfaced to users on your listing.

It must match reality — your SDKs (analytics, ads, crash reporting) often collect data on your behalf, so account for them too.

Two more common requirements:

• Privacy policy URL — required if your app handles personal or sensitive data. It must be a live, public web page.
• App access — if parts of your app are behind a login, you provide test credentials so reviewers can reach them. Skip this and review will likely fail.

Provide a working demo account and note any special steps reviewers need.

You declare your target age groups. If you include children, the app must comply with the Families policy and stricter ad/data rules.

You also declare whether the app contains ads. If it does, an "Contains ads" label appears on your listing. Being inaccurate here is a policy violation.

These declarations live in the App content section alongside data safety and content rating.

You can add a translated listing for every language you support — name, descriptions, screenshots and graphics per locale.

A localized listing dramatically improves discoverability and install rates in non-English markets. Match the locales your app actually ships strings for.

Tip: keep your in-app res/values-xx/strings.xml locales and your Play listing locales in sync so the experience is consistent.

Round out the listing with Store settings:

• Category — e.g. Education, Productivity, Games subcategory.
• Tags — help Play surface your app in the right places.
• Contact details — email (required), plus optional website and phone.

Pick the category that genuinely fits; the right category puts you in front of the right audience.

Before Play lets you submit to production, these must be green:

• Store listing text and all required graphics.
• Content rating questionnaire completed.
• Data safety form filled and accurate.
• Privacy policy URL (if applicable) and app access credentials.
• Target audience and ads declarations.
• At least one uploaded release (covered next lesson).

The Console shows a dashboard of remaining tasks — clear them all to unlock publishing.

Your app has a 80-character text field shown prominently near the top of the listing that strongly influences whether browsers tap install. Which field is this?

You now know how to set up an app on Play:

• Create the app and lock in a permanent applicationId.
• Write a compelling store listing: name, short and full descriptions, icon, feature graphic and screenshots.
• Complete required App content forms: content rating, data safety, target audience, ads, and privacy policy.
• Provide app access credentials so reviewers can sign in.
• Localize the listing to match your supported languages.

Next: uploading releases and rolling them out safely.