The two fields that decide whether anyone installs
On a phone, a Play listing shows the icon, the title and the short description above the fold. The full description is behind a tap that most people never make. So the 30-character title and the 80-character short description do nearly all the work, and both are cut at the limit with no warning beyond a red counter in the console. This preview counts as you type and renders the listing the way the store does, with your icon in place.
Writing them for a website app
- Title: your brand, then the category if there is room. "Yourshop — Furniture & Decor" fits; "Yourshop: The Best Online Furniture Store" does not, and Play's metadata policy rejects "best", "#1" and similar anyway.
- Short description: what the app lets people do, in one plain sentence. "Shop, track orders and get delivery updates." Not a slogan.
- Full description: up to 4,000 characters. Lead with what is in the app, then the native features — push notifications for order updates, offline product catalogue, one-tap reorder — because the reviewers checking Play's minimum-functionality policy read this too, and it should describe an app, not a website.
- Developer name: the business, as people know it.
Keywords do count in the title and short description for Play search, but stuffed titles are rejected under the metadata policy. One natural mention of what the app is for is the right amount.
What else the listing needs
A 512×512 icon with no transparency, a 1024×500 feature graphic, at least two phone screenshots, a privacy policy URL, and the content-rating and data-safety forms. The screenshot resizer produces every image size; the publishing guide walks through the rest of the console, including the closed-test requirement for new personal accounts.