# ASO Agency — Lesson 25: Google Play ASO: store listing requirements

Outcome: Create a Play-specific production plan rather than transplanting the iOS workflow.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Build a Play field inventory for your app.

Your response:

2. Identify three material differences from your iOS production pack.

Your response:

3. Assign owners for copy, graphics, language review and publication.

Your response:

## Scenario challenge

A colleague copies an iOS subtitle into the Play short description and calls the listing complete. Identify what needs a fresh decision: audience message, field role, full description, assets and Play-specific requirements.

Your reasoning:

## Handover

### Destination

Identify package, locale, default or custom listing and supported form factors.

Your evidence and decision:

### Field inventory

List current and proposed values, exact counts and linked platform requirements.

Your evidence and decision:

### Communication map

Explain the job of each field and how the visible promise stays coherent.

Your evidence and decision:

### Approval state

Name factual, language and publication reviewers and unresolved dependencies.

Your evidence and decision:

### Final verification

Check the actual console entries and visible listing against the approved pack.

Your evidence and decision:

## Submission check

- [ ] The workflow does not assume an iOS keyword field exists on Play.
- [ ] Identity claims are reviewed before production.
- [ ] Each field has a communication purpose and owner.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com