---
title: "Play Console | Skills We Assign For | Azendo"
description: "Play Console for Android releases — tracks, staged rollout, Android vitals, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/play-console/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# Play Console.

Play Console is Google's portal for Android applications: release tracks, staged rollouts, store listing, pre-launch reports run on real devices, and the vitals reporting that Google uses to rank apps on technical quality.

## Where Play Console fits on a long engagement.

The track model is Play Console's strongest feature. Internal, closed, open and production tracks let a build move through progressively wider audiences with the same artefact, which makes a genuinely staged release the default path rather than something a team has to construct.

Android vitals is the part teams underuse. Google measures crash rate, ANR rate, wakeups and startup time against thresholds, and an app exceeding them is demoted in Play's rankings. That makes stability a distribution concern rather than only a user-experience one, and vitals is the earliest place a regression shows up.

## What an assigned team does with Play Console.

Staged rollout only helps if someone is watching the numbers during it. A rollout increased on schedule regardless of vitals is not a staged rollout, it is a delayed full release with extra steps.

Owning that monitoring window is a defined responsibility rather than an assumption, and it sits with the assigned specialists as part of the release path described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use Play Console for.

* Progressive release through tracks One artefact moving from internal to production, so each stage tests the thing that will ship.
* Vitals watched during rollout Crash and ANR rates checked before each increase, so a bad build is halted rather than completed.
* Pre-launch reports on real devices Automated runs across a device matrix catching crashes before any user sees them.

## How Play Console capacity is assigned.

Android release operations sit inside the mobile capacity that builds the app, with vitals treated as a delivery metric rather than a dashboard nobody opens.

## Roles we assign Play Console for

* [Android Developer Mobile development](https://azendo.co/services/mobile-development/android-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in ci and delivery

* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [CodePush — skill we assign for](https://azendo.co/skills/codepush/)
* [Bitbucket Pipelines — skill we assign for](https://azendo.co/skills/bitbucket-pipelines/)
* [ArgoCD — skill we assign for](https://azendo.co/skills/argocd/)
* [GitOps — skill we assign for](https://azendo.co/skills/gitops/)
* [CircleCI — skill we assign for](https://azendo.co/skills/circleci/)
* [Feature flags — skill we assign for](https://azendo.co/skills/feature-flags/)

## Tell us what your roadmap needs Play Console for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)