Create a store listing that matches the product users receive
A review-friendly workflow for titles, descriptions, screenshots, claims, localization, and change control.
Describe the current build
Write from the behavior of the submitted build, not from a future roadmap. Every feature claim should point to a visible flow. Remove guarantees about approval, ranking, revenue, security, or availability that the product cannot prove.
Treat screenshots as evidence
Screenshots should show real interface states at supported dimensions. Avoid simulated notifications, fabricated ratings, unavailable features, and personal data. Keep a source record so the team can reproduce every image after the interface changes.
Localize meaning, not only words
A translated title can still fail if the screenshot, pricing statement, support link, or privacy explanation remains in another language. Review each locale as a complete customer journey and identify which pages intentionally remain in a beta language.
Control listing changes
Record the previous text, new text, reason, owner, and date. Re-run prohibited-claim and length checks after every edit. A listing change can also trigger a privacy, age-rating, or policy review.
Release-ready checklist
- Claims match the submitted build
- Images contain no personal data
- Every locale has working support and privacy links
- Paid relationships are disclosed
- Changes trigger a fresh policy check
This guide is written for planning and verification. Store rules and legal requirements can change; verify official requirements before submission.