Mamun Labs Learn
JourneyGlossary
esc
  • Try “map”, “flexbox” or “state”.
Log in
Start learning
Phase 8 · 4 / 4Your store listing and release
Phase 8Ship it to the Play Store
4 topics · 2–3 wks
  1. 1Icons, names and screenshots
  2. 2Building a release with EAS
  3. 3Play Console and internal testing
  4. 4Your store listing and release
JourneyPhase 8Your store listing and release
01 / 08Overview

Your store listing and release

You'll learn to write your app's store listing, make the graphics Google Play asks for, put a privacy policy online, and send your first release to production.

Why it mattersThe listing is your app's shop window. People decide in a few seconds whether to install it.
about 75 min·needs: Play Console and internal testing, Icons, names and screenshots, Put your page online
02 / 08

Watch & read

Start with the required ones. The others are there when you need them.

Docs
Create and set up your appPlay Console Help · 15 min · English
MMamun's noteRead "Set up your store listing and settings". It has the 30, 80 and 4000 character limits. Keep it open while you type.
Docs
Add preview assets to showcase your appPlay Console Help · 15 min · English
MMamun's noteThe rules for the icon, feature graphic, screenshots and short description, with examples of what not to write. Read the parts on the feature graphic and the short description.
DocsOptional
User data policyPlay Console Help · 10 min · English
MMamun's noteUse your browser search to find "privacy policy" on this long page. That part lists what your privacy page must say, and that it can't be a PDF.
DocsOptional
Prepare your app for reviewPlay Console Help · 10 min · English
MMamun's noteThe App content questions you answer before release. Use it as a checklist, one section at a time.
03 / 08

Explanation

Your app is on internal testing. Now you write the page that people see on Google Play: the store listing. Think of the poster outside a cinema. It has the name, one line that makes you curious, a few pictures, and the details in small letters.

The text has limits. As of October 2026, Google's help pages say:

  • App name: up to 30 characters.
  • Short description: up to 80 characters. Plain words, no emoji.
  • Full description: up to 4000 characters.

The graphics:

  • App icon: 512x512 PNG, up to 1024 KB. Export it from the same design as your app icon.
  • Feature graphic: 1024x500, JPEG or PNG without transparency. A wide banner with your name and logo. Make it in Figma or Canva.
  • Screenshots: at least two, up to eight for phones. The ones you cropped in the first topic of this phase.

Write the short description as one clear promise: what the app does for the person. Not "The best app", but "Track your daily habits and see your streak grow." Write the full description as short paragraphs: what it does, three or four features, and who made it.

Every app needs a privacy policy, even one that collects nothing. Google says it must be on an active, public web page, not a PDF. You already know how to do this: make a privacy.html page on your GitHub Pages site. Say what data the app keeps (for example "your habits stay on your phone"), what it sends (nothing), and how to contact you. Put the link in Play Console and inside the app, for example on a Settings or About screen.

https://nusrat-dev.github.io/daily-habits/privacy.html

When your closed test is done and Google gives you production access, make a release on the Production track. Choose the build, write release notes ("First version: add habits, mark them done, see your streak"), and send it for review.

People often fill the listing with words like "Best", "#1", "Top" or "Download now", and add emoji or "!!!" to the short description. Google's guidelines say not to use any of these in the short description or the graphics. Plain and honest works better, and it passes review.

When you read a store listing, check it like a stranger would: does the name say what it is, does the short description say what it does for you, and do the first two screenshots show the main screen?

Words to recognise
store listingshort descriptionfull descriptionfeature graphicprivacy policyreleaserelease notes
04 / 08

Code tour

Click a line number with a ring to read the note for that line.

store-listing.txt6 notes
1App name (12 of 30)
Daily Habits
Mentor note · line 2
The same name as in app.json. Short names fit under the icon and in search results.
3
4Short description (53 of 80)
Track your daily habits and watch your streak grow.
6
7Full description
Daily Habits helps you build small habits, one day at a time.
9
- Add a habit in two taps, like "Read 10 pages" or "Drink water"
11- Mark it done each day and see your streak
12- Works offline. Your habits stay on your phone.
13
Made by Nusrat Jahan, a CSE student in Dhaka, as her first app.
15
16Privacy policy
https://nusrat-dev.github.io/daily-habits/privacy.html
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Which short description is best for Google Play?
  2. 2 / 3Where should your privacy policy live?
  3. 3 / 3Play asks for a feature graphic. What size do you make?
06 / 08

Explain it back

Only you can see this. Log in to keep it.0 words
07 / 08

How confident are you with Your store listing and release?

08 / 08

Done

You can now
Write a store listing that fits Google Play's limits, host a privacy policy on GitHub Pages, and release a version to production.
Next: Plan your app Back to Phase 8
On this page
  1. 01Your store listing and release
  2. 02Watch & read
  3. 03Explanation
  4. 04Code tour
  5. 05Quick check
  6. 06Explain it back
  7. 07Confidence
  8. 08Done
Up next · 02 / 08Watch & read
Mamun Labs LearnFound a mistake on this page? Tell Mamun.
Mamun Labs Learn
JourneyGlossary
esc
  • Try “map”, “flexbox” or “state”.
Log in
Start learning
Log in to save your progress. Everything here works without an account.Log in to save progressLog in
Phase 8Ship it to the Play Store
4 topics · 2–3 wks
  1. 1Icons, names and screenshots
  2. 2Building a release with EAS
  3. 3Play Console and internal testing
  4. 4Your store listing and release
JourneyPhase 8Your store listing and release
01 / 08Overview

Your store listing and release

You'll learn to write your app's store listing, make the graphics Google Play asks for, put a privacy policy online, and send your first release to production.

Why it mattersThe listing is your app's shop window. People decide in a few seconds whether to install it.
about 75 min·needs: Play Console and internal testing, Icons, names and screenshots, Put your page online
02 / 08

Watch & read

Start with the required ones. The others are there when you need them.

Docs
Create and set up your appPlay Console Help · 15 min · English
MMamun's noteRead "Set up your store listing and settings". It has the 30, 80 and 4000 character limits. Keep it open while you type.
Docs
Add preview assets to showcase your appPlay Console Help · 15 min · English
MMamun's noteThe rules for the icon, feature graphic, screenshots and short description, with examples of what not to write. Read the parts on the feature graphic and the short description.
DocsOptional
User data policyPlay Console Help · 10 min · English
MMamun's noteUse your browser search to find "privacy policy" on this long page. That part lists what your privacy page must say, and that it can't be a PDF.
DocsOptional
Prepare your app for reviewPlay Console Help · 10 min · English
MMamun's noteThe App content questions you answer before release. Use it as a checklist, one section at a time.
03 / 08

Explanation

Your app is on internal testing. Now you write the page that people see on Google Play: the store listing. Think of the poster outside a cinema. It has the name, one line that makes you curious, a few pictures, and the details in small letters.

The text has limits. As of October 2026, Google's help pages say:

  • App name: up to 30 characters.
  • Short description: up to 80 characters. Plain words, no emoji.
  • Full description: up to 4000 characters.

The graphics:

  • App icon: 512x512 PNG, up to 1024 KB. Export it from the same design as your app icon.
  • Feature graphic: 1024x500, JPEG or PNG without transparency. A wide banner with your name and logo. Make it in Figma or Canva.
  • Screenshots: at least two, up to eight for phones. The ones you cropped in the first topic of this phase.

Write the short description as one clear promise: what the app does for the person. Not "The best app", but "Track your daily habits and see your streak grow." Write the full description as short paragraphs: what it does, three or four features, and who made it.

Every app needs a privacy policy, even one that collects nothing. Google says it must be on an active, public web page, not a PDF. You already know how to do this: make a privacy.html page on your GitHub Pages site. Say what data the app keeps (for example "your habits stay on your phone"), what it sends (nothing), and how to contact you. Put the link in Play Console and inside the app, for example on a Settings or About screen.

https://nusrat-dev.github.io/daily-habits/privacy.html

When your closed test is done and Google gives you production access, make a release on the Production track. Choose the build, write release notes ("First version: add habits, mark them done, see your streak"), and send it for review.

People often fill the listing with words like "Best", "#1", "Top" or "Download now", and add emoji or "!!!" to the short description. Google's guidelines say not to use any of these in the short description or the graphics. Plain and honest works better, and it passes review.

When you read a store listing, check it like a stranger would: does the name say what it is, does the short description say what it does for you, and do the first two screenshots show the main screen?

Words to recognise
store listingshort descriptionfull descriptionfeature graphicprivacy policyreleaserelease notes
04 / 08

Code tour

Click a line number with a ring to read the note for that line.

store-listing.txt6 notes
1App name (12 of 30)
Daily Habits
Mentor note · line 2
The same name as in app.json. Short names fit under the icon and in search results.
3
4Short description (53 of 80)
Track your daily habits and watch your streak grow.
6
7Full description
Daily Habits helps you build small habits, one day at a time.
9
- Add a habit in two taps, like "Read 10 pages" or "Drink water"
11- Mark it done each day and see your streak
12- Works offline. Your habits stay on your phone.
13
Made by Nusrat Jahan, a CSE student in Dhaka, as her first app.
15
16Privacy policy
https://nusrat-dev.github.io/daily-habits/privacy.html
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Which short description is best for Google Play?
  2. 2 / 3Where should your privacy policy live?
  3. 3 / 3Play asks for a feature graphic. What size do you make?
06 / 08

Explain it back

Only you can see this. Log in to keep it.0 words
07 / 08

How confident are you with Your store listing and release?

08 / 08

Done

You can now
Write a store listing that fits Google Play's limits, host a privacy policy on GitHub Pages, and release a version to production.
Next: Plan your app Back to Phase 8
On this page
  1. 01Your store listing and release
  2. 02Watch & read
  3. 03Explanation
  4. 04Code tour
  5. 05Quick check
  6. 06Explain it back
  7. 07Confidence
  8. 08Done
Up next · 02 / 08Watch & read

Your app is on internal testing. Now you write the page that people see on Google Play: the store listing. Think of the poster outside a cinema. It has the name, one line that makes you curious, a few pictures, and the details in small letters.

The text has limits. As of October 2026, Google's help pages say:

  • App name: up to 30 characters.
  • Short description: up to 80 characters. Plain words, no emoji.
  • Full description: up to 4000 characters.

The graphics:

  • App icon: 512x512 PNG, up to 1024 KB. Export it from the same design as your app icon.
  • Feature graphic: 1024x500, JPEG or PNG without transparency. A wide banner with your name and logo. Make it in Figma or Canva.
  • Screenshots: at least two, up to eight for phones. The ones you cropped in the first topic of this phase.

Write the short description as one clear promise: what the app does for the person. Not "The best app", but "Track your daily habits and see your streak grow." Write the full description as short paragraphs: what it does, three or four features, and who made it.

Every app needs a privacy policy, even one that collects nothing. Google says it must be on an active, public web page, not a PDF. You already know how to do this: make a privacy.html page on your GitHub Pages site. Say what data the app keeps (for example "your habits stay on your phone"), what it sends (nothing), and how to contact you. Put the link in Play Console and inside the app, for example on a Settings or About screen.

https://nusrat-dev.github.io/daily-habits/privacy.html

When your closed test is done and Google gives you production access, make a release on the Production track. Choose the build, write release notes ("First version: add habits, mark them done, see your streak"), and send it for review.

People often fill the listing with words like "Best", "#1", "Top" or "Download now", and add emoji or "!!!" to the short description. Google's guidelines say not to use any of these in the short description or the graphics. Plain and honest works better, and it passes review.

When you read a store listing, check it like a stranger would: does the name say what it is, does the short description say what it does for you, and do the first two screenshots show the main screen?

Words to recognise
store listingshort descriptionfull descriptionfeature graphicprivacy policyreleaserelease notes

Your app is on internal testing. Now you write the page that people see on Google Play: the store listing. Think of the poster outside a cinema. It has the name, one line that makes you curious, a few pictures, and the details in small letters.

The text has limits. As of October 2026, Google's help pages say:

  • App name: up to 30 characters.
  • Short description: up to 80 characters. Plain words, no emoji.
  • Full description: up to 4000 characters.

The graphics:

  • App icon: 512x512 PNG, up to 1024 KB. Export it from the same design as your app icon.
  • Feature graphic: 1024x500, JPEG or PNG without transparency. A wide banner with your name and logo. Make it in Figma or Canva.
  • Screenshots: at least two, up to eight for phones. The ones you cropped in the first topic of this phase.

Write the short description as one clear promise: what the app does for the person. Not "The best app", but "Track your daily habits and see your streak grow." Write the full description as short paragraphs: what it does, three or four features, and who made it.

Every app needs a privacy policy, even one that collects nothing. Google says it must be on an active, public web page, not a PDF. You already know how to do this: make a privacy.html page on your GitHub Pages site. Say what data the app keeps (for example "your habits stay on your phone"), what it sends (nothing), and how to contact you. Put the link in Play Console and inside the app, for example on a Settings or About screen.

https://nusrat-dev.github.io/daily-habits/privacy.html

When your closed test is done and Google gives you production access, make a release on the Production track. Choose the build, write release notes ("First version: add habits, mark them done, see your streak"), and send it for review.

People often fill the listing with words like "Best", "#1", "Top" or "Download now", and add emoji or "!!!" to the short description. Google's guidelines say not to use any of these in the short description or the graphics. Plain and honest works better, and it passes review.

When you read a store listing, check it like a stranger would: does the name say what it is, does the short description say what it does for you, and do the first two screenshots show the main screen?

Words to recognise
store listingshort descriptionfull descriptionfeature graphicprivacy policyreleaserelease notes