Google Play tracks

The Tracks tab is the Google Play equivalent of Apple’s Builds and Review tabs. It shows your release tracks and exposes the Play edit lifecycle.

Note

The Tracks tab is Google-only. Apple uses the Builds and Review tabs.

---

Play edit lifecycle

Google groups all metadata, image, and track writes inside an edit — a change set you open, apply changes to, and commit. The Play edit lifecycle card at the top of the Tracks tab gives you manual control of that change set.

State	Action	Result
No edit open	Open Edit	Starts a change set (“Opened edit <id>”)
Edit open	Validate	Preflight-checks the edit (“Edit validates”)
Edit open	Commit	Publishes the changes (“Edit committed — changes live on Play”)
Edit open	Discard	Throws the edit away (“Edit discarded”)

An open edit shows its id and an expiry countdown. Stale edits expire after 7 days — once expired, discard it and open a fresh one.

Note

Editing metadata on the Metadata tab does not require you to use this card — Athena opens and commits an edit automatically for metadata writes. The lifecycle card is for operators who want explicit, manual control of a change set.

---

Tracks (read-only)

Each track (for example internal, alpha, beta, production, or a custom closed-testing track) is shown as a card listing its releases. Each release shows:

• Release name and status
• Version codes
• Rollout percentage (when a staged rollout is set)
• Target countries (when country targeting is set)
• Release notes per locale (expandable)

Note

The tracks list is read-only today. Write actions such as changing the rollout percentage or halting a release are planned; the only write surface here now is the Play edit lifecycle card above.