Why preview
The Play Console gives you form fields. What users see is a phone screen where the title is cut after two words in search results, the short description is the only text above the fold, and only the first two screenshots are visible. Seeing that layout while the text is still editable saves a round of "why does it look like that" after publishing — and store listing changes, unlike app updates, still go through review.
What to check
- Title. Thirty characters allowed; roughly twenty display in search results and on the home screen. The first two words carry the meaning. "Rosie's Bakery" beats "Rosie's — Order Fresh Bread Online".
- Short description. Eighty characters, shown under the title before "About this app". It should say what the app does for the user. Not a slogan.
- Icon at listing size. Your 512×512 icon appears at around 60 px in lists. Fine detail disappears.
- First two screenshots. Do they show the app doing its main job, without a browser bar, with readable captions?
- Full description opening line. Only the first line or two show before "Read more". Lead with the one thing.
- Developer name. Must be your legal or trading name as registered in the console; it is displayed and reviewers compare it to the brand in the app.
What Play adds that isn't in the preview
The content rating, the Data safety card, install count and ratings (after launch), the "Similar apps" row and the developer contact block. The Data safety card in particular is prominent and is generated from your form answers — see the Data safety guide — so a listing that says "collects no data" next to a description mentioning notifications and analytics looks contradictory to users and reviewers alike.
Use it for review, not as a contract
Google adjusts the store layout periodically. The preview reflects the current phone design closely enough for proportions and truncation. Export it and send it to whoever signs off on the listing; it is faster and safer than granting console access.