ReferencePlay Console

Google Play Console: A Walkthrough for New Developers

How Play Console is organised: the dashboard task list, the setup journey from app details to production, and where testing and publishing live.

Reviewed August 17, 2026May change — always verify in Play Console3 min read3 official sources

Written & maintained by AppsTestLabAbout AppsTestLabHow we research

A phone with a checklist showing Google Play setup steps
A phone with a checklist showing Google Play setup steps
On this page
  1. The dashboard: your setup guide
  2. The setup journey
  3. Where testing lives
  4. Publishing, explained
  5. After launch: the dashboard becomes analytics

Play Console is where your app becomes a real Play Store app: setup, testing, releases, and performance all happen here. The surface looks dense, but the logic is simple — the Dashboard walks you through every mandatory step in order, and this guide explains what you'll meet along the way.

The dashboard: your setup guide

When you open an app, the Dashboard shows the categories and tasks that still need work: app details, store listing content, app content, testing, and release. Completed tasks get a green tick, and a progress bar tracks the setup as a whole. You must complete the mandatory tasks before the app can launch on Google Play.

The setup journey

  1. App details and categorization

    Choose the app category and tags, and provide contact details — your support email is required, website and phone are optional.

  1. Store listing

    Write the title, short and full descriptions, and add screenshots and a video. The same listing is shown across all tracks, including testing tracks — testers see it too.

  1. App content

    The App content page covers the policy-facing parts: data safety, privacy policy, ads, content rating, and target audience. Anything needed for the review — like a demo account — is prepared here.

  1. Testing and release

    Set up internal and closed tests, roll out a release to a track, gather feedback, and eventually roll out to production. For personal accounts created after November 13, 2023, testing tasks are a hard requirement before production access.

Where testing lives

Testing > Internal testing, Closed testing, and Open testing are the three track areas. Internal gives up to 100 testers one of the fastest feedback loops; closed testing is the controlled group that the new-account requirement is built on; open testing surfaces your test app on Play itself. Releases are created the same way on every track.

Publishing, explained

Play offers two publishing modes. Standard publishing makes reviewed changes go live immediately after approval. Managed publishing holds your changes until you explicitly push them — useful when you want a release to go out at a planned moment. Either way, changes that need review first pass through the Publishing overview page.

After launch: the dashboard becomes analytics

Once the app is live, the Dashboard fills in with performance data — installs, uninstalls, ratings, crashes, and key insights over time. You can customise which metrics appear, and the same pages keep serving releases, updates, and managed publishing decisions.

Sources & references

Official Google documentation

These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.

Get help doing this

AppsTestLab can run your testing for you

Ready to test?

5,000+ apps tested. A 99% historical approval rate. And a 100% money-back guarantee.

Tell us about your app and we'll confirm the right testing approach. One WhatsApp message to start, no complicated setup.

Guarantee applies to eligible app testing orders · Google makes the final approval decision

Chat on WhatsApp