App development Tutorial

How to write a Google Play store listing that gets installs

A plain guide to the title, descriptions, icon, screenshots and policy details of a Google Play listing, and how to check it before you publish.

Arefin Khaled · Updated · 7 min read

A Play Store listing does two jobs at once. It convinces a person who has never heard of your app to tap Install, and it tells Google what the app is about so it can show it to the right searchers. Most developers spend months on the app and ten minutes on the listing, and it shows.

This guide goes through each part of a listing, what to write, what to avoid, and how to check your work before you publish.

Part 1: Title and short description

  1. Title: put the app's name first, then a few plain words about what it does. Keep it readable. Google Play sets limits on title length, so check the current limit in Play Console as you type.
  2. Short description: one sentence that says what the user gets. It appears in search results, so make the first words count.
  3. Avoid hype: words like "best" or "number 1", or emoji and symbols in the title, can break the policy rules.

Part 2: The long description

Open with two lines that answer "what is this and who is it for?" Then explain the main features in short paragraphs or a small list. Add a line on whether the app works offline, whether it is free, and whether it has ads or in-app purchases.

Part 3: Icon, screenshots and the feature graphic

AssetWhat to do
Icon512 x 512 px, simple, readable when small, no screenshots inside it
Feature graphic1024 x 500 px, a clear message, little text
ScreenshotsReal screens in the order a user would see them, with short captions
Video (optional)A short demo that shows the app working

Check the current size and format rules in Play Console Help before you export.

Part 4: Category, contact and policy details

Choose the category that matches the main use of the app, not the one with the least competition. Add a working contact email, a developer website if you have one, and a public privacy policy link. Our privacy policy checklist shows what that page should cover.

Part 5: Ratings and replies

Reply to reviews politely, especially the critical ones. A calm reply that explains a fix shows new visitors that someone is looking after the app. Ask for feedback inside the app at a good moment, such as after the user has completed a task, and never pressure people for five stars.

Part 6: Before you publish

  1. Read the whole listing out loud once.
  2. Check that every feature mentioned really exists.
  3. Look at the listing on a phone, not just a computer.
  4. Compare screenshots with the current version of the app.
  5. Confirm the privacy policy and Data safety answers match.

Frequently asked questions

Can I change the listing after publishing?

Yes. You can edit it in Play Console and publish the change, and some edits go through review.

Should I translate the listing?

If you have users in other languages, a translated listing helps them. A good translation is better than a machine one pasted in without reading.

Do I need a video?

No, but a short demo can help people understand the app quickly.

How often should I update the listing?

Whenever the app changes in a way users would notice.

A good listing is mostly clear writing and honest pictures. Do those two things well and the rest follows.

Share this article Facebook LinkedIn X WhatsApp
Arefin Khaled

A lawyer in Bangladesh who builds Android apps and websites, and researches environment, climate and human rights.

More about me →

Keep reading