Why preview a listing for a web app
If your web app never goes near Google Play, you don't need this page — installation happens on your own site. It exists for the other case: you have wrapped the PWA as a Trusted Web Activity and are about to fill in a store listing for the first time. The Play Console form gives you text boxes and no picture of the result until the listing is live. This preview shows you the phone layout while everything is still editable.
What to check in the preview
- Title truncation. Thirty characters is the limit, but search results and the home screen cut off well before that. The first two words should carry the meaning.
- Short description as a hook. It sits directly under the title above the fold. Read it as a stranger: does it say what the app does for me?
- Icon at listing size. The 512×512 icon is displayed much smaller. Fine detail vanishes; check it still reads. The icon resizer shows the small sizes too.
- Screenshot order. The first two are visible without scrolling. Put the screen that shows the core value first, not the splash or login screen.
- Consistency with the website. The listing should look like the site people already know. Same colours, same name, same voice.
Fields the preview does not show
Play also displays the content rating, the "Data safety" summary, the developer's contact details and, after launch, ratings and reviews. None of that is designable here, but all of it is required — the TWA checklist covers each form.
Sharing the preview
Export the preview as a PNG and send it to whoever needs to approve the listing. It is quicker than a screen-share of the Play Console and avoids giving people console access just to look.