Mamun Labs Learn
JourneyGlossary
esc
  • Try “map”, “flexbox” or “state”.
Log in
Start learning
Phase 8 · 3 / 4Play Console and internal testing
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 8Play Console and internal testing
01 / 08Overview

Play Console and internal testing

You'll learn to open a Google Play developer account, upload your first build to internal testing, and plan the closed test Google asks new accounts for.

Why it mattersGoogle has rules before an app can go public. If you know them on day one, you don't lose two weeks waiting.
about 90 min·needs: Building a release with EAS
02 / 08

Watch & read

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

Video
How to create a production build for AndroidExpo · YouTube · 7 min · English
MMamun's noteWatch 0:00 to 6:29: making the production build, creating the app in Play Console, an internal release, and testing on a real phone. Skip the service account part after 6:29. Uploading by hand is enough for now.
Docs
App testing requirements for new personal developer accountsPlay Console Help · 10 min · English
MMamun's noteThe rule about 12 testers for 14 days, from Google itself. Read it all, including the tips at the end. Check it again before you start, because Google changes this rule.
Docs
Get started with Play ConsolePlay Console Help · 10 min · English
MMamun's noteRead this before you pay: the fee, which cards work, and what ID Google asks for. Keep your ID and card in your own legal name.
DocsOptional
Meet Google Play's target API level requirementAndroid Developers · 5 min · English
MMamun's noteRead only the first box with the current dates. If Play shows a target API warning, this page says what level it wants. Skip the rest.
03 / 08

Explanation

You have an .aab from EAS. Now you need a place to put it. That place is the Play Console, Google's website for app developers.

Think of Google Play as a big market. Before you get a shop at the front, Google wants to know who you are, and that your app works for real people. So you start in the back room with friends, then a small group, then the front of the market.

1. The account. Open play.google.com/console and choose a personal account. As of October 2026, Google's help pages say:

  • There is a US$25 registration fee, paid once.
  • You must be at least 18, and Google may ask for a government ID with your legal name.
  • New personal accounts must also prove they have an Android phone, using the Play Console app.

Pay with a Visa or Mastercard that works for international payments, like a dual-currency card from your bank. Google says prepaid cards are not accepted, and bKash is not on its list. If you are stuck, ask Mamun before you pay with someone else's card. The name on the account must be your legal name.

2. The tracks. A track is a group of people who get a version of your app.

  • Internal testing: a small group you invite by email. The fastest way to check your build.
  • Closed testing: a bigger, invited group.
  • Open testing: anyone can join from Google Play.
  • Production: everyone.

3. The closed test rule. For personal accounts made after 13 November 2023, Google says you need a closed test with at least 12 testers, opted in for at least 14 days in a row, before you can apply for production. Testers who leave early don't count. Then you apply from the Dashboard, and Google's review usually takes up to seven days.

4. App content. Under "App content", Play asks questions about your app: a privacy policy link, app access (if the app needs a login, you give Google a test login), ads, the content rating questionnaire, target audience, and the Data safety form, which says what data your app collects. Answer honestly. A habit tracker that keeps everything on the phone collects very little.

Play also has a target API level rule. Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Your Expo SDK version sets this for you, so keep it up to date. The table on the Expo "SDK reference" page shows which SDK targets which level. If Play shows a target API warning, your Expo SDK is too old.

People often finish the app first and look for 12 testers at the end. Then they wait two more weeks. Start the closed test as soon as your app works, and ask classmates who will really use it. Google asks you to describe their feedback when you apply, so give them a way to reply, like a WhatsApp group.

When you read the Play Console Dashboard, look for the list of setup tasks. Each has a tick when it is done. Anything without a tick is why your release is not going out.

Words to recognise
Play Consoledeveloper accountinternal testingclosed testingopen testingproductiontesterData safetycontent ratingtarget API level
04 / 08

Code tour

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

play-console-checklist.txt6 notes
1Daily Habits: Play Console checklist (Nusrat, October 2026)
2
[x] Personal developer account, US$25 paid once, ID verified
Mentor note · line 3
The fee is paid once, not every year. Use a card that works for international payments, in your own name.
4[x] Android phone verified with the Play Console app
[x] App created, package com.nusratdev.habits
[x] Internal testing: production .aab uploaded, 3 friends testing
[ ] App content: privacy policy, app access, ads, content rating,
8 target audience, Data safety
[ ] Closed testing: 12+ testers opted in
Day 1: 20 Oct Day 14: 2 Nov
11[ ] Apply for production on the Dashboard
12[ ] Review, usually up to 7 days
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your personal account is new. 12 friends join your closed test, but 2 leave on day 9. Can you apply for production on day 14?
  2. 2 / 3You just made your first production .aab. What is the quickest way to check it on your friends' phones through Google Play?
  3. 3 / 3Your habit tracker keeps all data on the phone and sends nothing. Do you still fill in the Data safety form before going public?
06 / 08

Explain it back

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

How confident are you with Play Console and internal testing?

08 / 08

Done

You can now
Set up a Play Console account, put a build on internal testing for your friends, and plan a closed test with enough testers for long enough.
Next: Your store listing and release Back to Phase 8
On this page
  1. 01Play Console and internal testing
  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 8Play Console and internal testing
01 / 08Overview

Play Console and internal testing

You'll learn to open a Google Play developer account, upload your first build to internal testing, and plan the closed test Google asks new accounts for.

Why it mattersGoogle has rules before an app can go public. If you know them on day one, you don't lose two weeks waiting.
about 90 min·needs: Building a release with EAS
02 / 08

Watch & read

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

Video
How to create a production build for AndroidExpo · YouTube · 7 min · English
MMamun's noteWatch 0:00 to 6:29: making the production build, creating the app in Play Console, an internal release, and testing on a real phone. Skip the service account part after 6:29. Uploading by hand is enough for now.
Docs
App testing requirements for new personal developer accountsPlay Console Help · 10 min · English
MMamun's noteThe rule about 12 testers for 14 days, from Google itself. Read it all, including the tips at the end. Check it again before you start, because Google changes this rule.
Docs
Get started with Play ConsolePlay Console Help · 10 min · English
MMamun's noteRead this before you pay: the fee, which cards work, and what ID Google asks for. Keep your ID and card in your own legal name.
DocsOptional
Meet Google Play's target API level requirementAndroid Developers · 5 min · English
MMamun's noteRead only the first box with the current dates. If Play shows a target API warning, this page says what level it wants. Skip the rest.
03 / 08

Explanation

You have an .aab from EAS. Now you need a place to put it. That place is the Play Console, Google's website for app developers.

Think of Google Play as a big market. Before you get a shop at the front, Google wants to know who you are, and that your app works for real people. So you start in the back room with friends, then a small group, then the front of the market.

1. The account. Open play.google.com/console and choose a personal account. As of October 2026, Google's help pages say:

  • There is a US$25 registration fee, paid once.
  • You must be at least 18, and Google may ask for a government ID with your legal name.
  • New personal accounts must also prove they have an Android phone, using the Play Console app.

Pay with a Visa or Mastercard that works for international payments, like a dual-currency card from your bank. Google says prepaid cards are not accepted, and bKash is not on its list. If you are stuck, ask Mamun before you pay with someone else's card. The name on the account must be your legal name.

2. The tracks. A track is a group of people who get a version of your app.

  • Internal testing: a small group you invite by email. The fastest way to check your build.
  • Closed testing: a bigger, invited group.
  • Open testing: anyone can join from Google Play.
  • Production: everyone.

3. The closed test rule. For personal accounts made after 13 November 2023, Google says you need a closed test with at least 12 testers, opted in for at least 14 days in a row, before you can apply for production. Testers who leave early don't count. Then you apply from the Dashboard, and Google's review usually takes up to seven days.

4. App content. Under "App content", Play asks questions about your app: a privacy policy link, app access (if the app needs a login, you give Google a test login), ads, the content rating questionnaire, target audience, and the Data safety form, which says what data your app collects. Answer honestly. A habit tracker that keeps everything on the phone collects very little.

Play also has a target API level rule. Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Your Expo SDK version sets this for you, so keep it up to date. The table on the Expo "SDK reference" page shows which SDK targets which level. If Play shows a target API warning, your Expo SDK is too old.

People often finish the app first and look for 12 testers at the end. Then they wait two more weeks. Start the closed test as soon as your app works, and ask classmates who will really use it. Google asks you to describe their feedback when you apply, so give them a way to reply, like a WhatsApp group.

When you read the Play Console Dashboard, look for the list of setup tasks. Each has a tick when it is done. Anything without a tick is why your release is not going out.

Words to recognise
Play Consoledeveloper accountinternal testingclosed testingopen testingproductiontesterData safetycontent ratingtarget API level
04 / 08

Code tour

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

play-console-checklist.txt6 notes
1Daily Habits: Play Console checklist (Nusrat, October 2026)
2
[x] Personal developer account, US$25 paid once, ID verified
Mentor note · line 3
The fee is paid once, not every year. Use a card that works for international payments, in your own name.
4[x] Android phone verified with the Play Console app
[x] App created, package com.nusratdev.habits
[x] Internal testing: production .aab uploaded, 3 friends testing
[ ] App content: privacy policy, app access, ads, content rating,
8 target audience, Data safety
[ ] Closed testing: 12+ testers opted in
Day 1: 20 Oct Day 14: 2 Nov
11[ ] Apply for production on the Dashboard
12[ ] Review, usually up to 7 days
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your personal account is new. 12 friends join your closed test, but 2 leave on day 9. Can you apply for production on day 14?
  2. 2 / 3You just made your first production .aab. What is the quickest way to check it on your friends' phones through Google Play?
  3. 3 / 3Your habit tracker keeps all data on the phone and sends nothing. Do you still fill in the Data safety form before going public?
06 / 08

Explain it back

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

How confident are you with Play Console and internal testing?

08 / 08

Done

You can now
Set up a Play Console account, put a build on internal testing for your friends, and plan a closed test with enough testers for long enough.
Next: Your store listing and release Back to Phase 8
On this page
  1. 01Play Console and internal testing
  2. 02Watch & read
  3. 03Explanation
  4. 04Code tour
  5. 05Quick check
  6. 06Explain it back
  7. 07Confidence
  8. 08Done
Up next · 02 / 08Watch & read

You have an .aab from EAS. Now you need a place to put it. That place is the Play Console, Google's website for app developers.

Think of Google Play as a big market. Before you get a shop at the front, Google wants to know who you are, and that your app works for real people. So you start in the back room with friends, then a small group, then the front of the market.

1. The account. Open play.google.com/console and choose a personal account. As of October 2026, Google's help pages say:

  • There is a US$25 registration fee, paid once.
  • You must be at least 18, and Google may ask for a government ID with your legal name.
  • New personal accounts must also prove they have an Android phone, using the Play Console app.

Pay with a Visa or Mastercard that works for international payments, like a dual-currency card from your bank. Google says prepaid cards are not accepted, and bKash is not on its list. If you are stuck, ask Mamun before you pay with someone else's card. The name on the account must be your legal name.

2. The tracks. A track is a group of people who get a version of your app.

  • Internal testing: a small group you invite by email. The fastest way to check your build.
  • Closed testing: a bigger, invited group.
  • Open testing: anyone can join from Google Play.
  • Production: everyone.

3. The closed test rule. For personal accounts made after 13 November 2023, Google says you need a closed test with at least 12 testers, opted in for at least 14 days in a row, before you can apply for production. Testers who leave early don't count. Then you apply from the Dashboard, and Google's review usually takes up to seven days.

4. App content. Under "App content", Play asks questions about your app: a privacy policy link, app access (if the app needs a login, you give Google a test login), ads, the content rating questionnaire, target audience, and the Data safety form, which says what data your app collects. Answer honestly. A habit tracker that keeps everything on the phone collects very little.

Play also has a target API level rule. Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Your Expo SDK version sets this for you, so keep it up to date. The table on the Expo "SDK reference" page shows which SDK targets which level. If Play shows a target API warning, your Expo SDK is too old.

People often finish the app first and look for 12 testers at the end. Then they wait two more weeks. Start the closed test as soon as your app works, and ask classmates who will really use it. Google asks you to describe their feedback when you apply, so give them a way to reply, like a WhatsApp group.

When you read the Play Console Dashboard, look for the list of setup tasks. Each has a tick when it is done. Anything without a tick is why your release is not going out.

Words to recognise
Play Consoledeveloper accountinternal testingclosed testingopen testingproductiontesterData safetycontent ratingtarget API level

You have an .aab from EAS. Now you need a place to put it. That place is the Play Console, Google's website for app developers.

Think of Google Play as a big market. Before you get a shop at the front, Google wants to know who you are, and that your app works for real people. So you start in the back room with friends, then a small group, then the front of the market.

1. The account. Open play.google.com/console and choose a personal account. As of October 2026, Google's help pages say:

  • There is a US$25 registration fee, paid once.
  • You must be at least 18, and Google may ask for a government ID with your legal name.
  • New personal accounts must also prove they have an Android phone, using the Play Console app.

Pay with a Visa or Mastercard that works for international payments, like a dual-currency card from your bank. Google says prepaid cards are not accepted, and bKash is not on its list. If you are stuck, ask Mamun before you pay with someone else's card. The name on the account must be your legal name.

2. The tracks. A track is a group of people who get a version of your app.

  • Internal testing: a small group you invite by email. The fastest way to check your build.
  • Closed testing: a bigger, invited group.
  • Open testing: anyone can join from Google Play.
  • Production: everyone.

3. The closed test rule. For personal accounts made after 13 November 2023, Google says you need a closed test with at least 12 testers, opted in for at least 14 days in a row, before you can apply for production. Testers who leave early don't count. Then you apply from the Dashboard, and Google's review usually takes up to seven days.

4. App content. Under "App content", Play asks questions about your app: a privacy policy link, app access (if the app needs a login, you give Google a test login), ads, the content rating questionnaire, target audience, and the Data safety form, which says what data your app collects. Answer honestly. A habit tracker that keeps everything on the phone collects very little.

Play also has a target API level rule. Since 31 August 2026, new apps and updates must target Android 16 (API level 36). Your Expo SDK version sets this for you, so keep it up to date. The table on the Expo "SDK reference" page shows which SDK targets which level. If Play shows a target API warning, your Expo SDK is too old.

People often finish the app first and look for 12 testers at the end. Then they wait two more weeks. Start the closed test as soon as your app works, and ask classmates who will really use it. Google asks you to describe their feedback when you apply, so give them a way to reply, like a WhatsApp group.

When you read the Play Console Dashboard, look for the list of setup tasks. Each has a tick when it is done. Anything without a tick is why your release is not going out.

Words to recognise
Play Consoledeveloper accountinternal testingclosed testingopen testingproductiontesterData safetycontent ratingtarget API level