Mamun Labs Learn
JourneyGlossary
esc
  • Try “map”, “flexbox” or “state”.
Log in
Start learning
Phase 9 · 3 / 3Launch and share
Phase 9Capstone
3 topics · 4+ wks
  1. 1Plan your app
  2. 2Build with reviews
  3. 3Launch and share
JourneyPhase 9Launch and share
01 / 08Overview

Launch and share

You'll learn to share your app with a Play Store link, a short demo video and a README with screenshots, and to ask for feedback politely.

Why it mattersYou built and shipped a real app. Showing it well is how teachers, friends and future employers find out.
about 90 min·needs: Build with reviews, Your store listing and release
02 / 08

Watch & read

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

Docs
About the repository README fileGitHub Docs · 5 min · English
MMamun's noteWhat a README is and where GitHub shows it. Read the part on what a README should say. Skip the auto-generated table of contents.
Docs
Basic writing and formatting syntaxGitHub Docs · 15 min · English
MMamun's noteRead Headings, Links, Images and Lists. That is all your README needs. Keep it open while you write.
DocsOptional
Take a screenshot or record your screen on your Android deviceAndroid Help · 5 min · English
MMamun's noteHow to use the screen recorder that is already on your phone. Turn on "Show touches" so people can see where you tap.
DocsOptional
Linking to Google PlayAndroid Developers · 5 min · English
MMamun's noteThe official format of the Play link. Read only the part on linking to a store listing. Skip the Kotlin code.
03 / 08

Explanation

Your app is live on Google Play. Take a moment. You started with "what does a computer do", and now strangers can install something you made. Now you tell people, in a way that makes them want to try it.

Think of a new fuchka stall. A sign helps, but what brings people is a friend saying "try this one" and showing a photo. Your link, your video and your README are that friend.

1. The Play link. Every app has one, made from its package:

https://play.google.com/store/apps/details?id=com.tanvir.messhisab

2. A short demo video. Use the screen recorder built into Android: swipe down for Quick Settings and tap Screen record. Show one real task from start to end, like adding an expense and seeing the totals change. Keep it under a minute. No music needed, and no long intro.

3. A README. The README.md file is the front page of your repo on GitHub. Write it in Markdown: # for a heading, - for a list, and ![text](file.png) for a picture. It says what the app is, shows two screenshots, gives the Play link, and lists what you used to build it.

4. The post. On LinkedIn, write a short story: what problem, who it is for, one thing you learned, the link and the video. In a Facebook group, read the rules first. Many groups allow project posts only on certain days, or not at all. Post once, not in ten groups on the same day.

5. Ask for feedback. Ask a clear question: "What was confusing the first time you opened it?" is better than "How is it?". Put every answer in one list. Fix the most common one first, and ship an update with release notes.

People often post "Please download my app and give 5 stars". That asks for a favour, not feedback. Five stars from friends don't tell you what to fix. Ask people to try it and tell you honestly what they think.

When you read your own README, open it on your phone like a stranger would. Can you tell what the app does in five seconds? Do the pictures load? Does the Play link open the right app?

Words to recognise
READMEMarkdowndemo videoscreen recordingPlay Store linkfeedback
04 / 08

Code tour

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

README.md7 notes
# Mess Hisab
Mentor note · line 1
The app's name as the main heading. One "#" makes the biggest heading in Markdown.
2
Split bazar costs in your mess. Add what you paid, and see who owes what at the end of the month.
4
[Get it on Google Play](https://play.google.com/store/apps/details?id=com.tanvir.messhisab)
· [Watch the 45-second demo](https://youtu.be/your-video-id)
7
![Expense list with totals per member](screenshots/expenses.png)
9![Adding a new expense](screenshots/add-expense.png)
10
11## Features
12- Add an expense in a few taps
13- See the total for each member
14- Works offline. Your data stays on your phone.
15
16## Built with
React Native, Expo, TypeScript, AsyncStorage. Built during Mamun Labs Learn, with reviews from Mamun.
18
19## Feedback
Found something confusing? Open an issue, or write to tanvir.dev@example.com.
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your package is com.tanvir.messhisab. Which link opens your app on Google Play?
  2. 2 / 3Which question gets the most useful feedback?
  3. 3 / 3Your README has ![Home](Screenshots/home.png). The folder in the repo is screenshots. What happens on GitHub?
06 / 08

Explain it back

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

How confident are you with Launch and share?

08 / 08

Done

You can now
Share your app with a working Play link, a one-minute demo and a clear README, and collect feedback you can act on.
Back to Phase 9
On this page
  1. 01Launch and share
  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 9Capstone
3 topics · 4+ wks
  1. 1Plan your app
  2. 2Build with reviews
  3. 3Launch and share
JourneyPhase 9Launch and share
01 / 08Overview

Launch and share

You'll learn to share your app with a Play Store link, a short demo video and a README with screenshots, and to ask for feedback politely.

Why it mattersYou built and shipped a real app. Showing it well is how teachers, friends and future employers find out.
about 90 min·needs: Build with reviews, Your store listing and release
02 / 08

Watch & read

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

Docs
About the repository README fileGitHub Docs · 5 min · English
MMamun's noteWhat a README is and where GitHub shows it. Read the part on what a README should say. Skip the auto-generated table of contents.
Docs
Basic writing and formatting syntaxGitHub Docs · 15 min · English
MMamun's noteRead Headings, Links, Images and Lists. That is all your README needs. Keep it open while you write.
DocsOptional
Take a screenshot or record your screen on your Android deviceAndroid Help · 5 min · English
MMamun's noteHow to use the screen recorder that is already on your phone. Turn on "Show touches" so people can see where you tap.
DocsOptional
Linking to Google PlayAndroid Developers · 5 min · English
MMamun's noteThe official format of the Play link. Read only the part on linking to a store listing. Skip the Kotlin code.
03 / 08

Explanation

Your app is live on Google Play. Take a moment. You started with "what does a computer do", and now strangers can install something you made. Now you tell people, in a way that makes them want to try it.

Think of a new fuchka stall. A sign helps, but what brings people is a friend saying "try this one" and showing a photo. Your link, your video and your README are that friend.

1. The Play link. Every app has one, made from its package:

https://play.google.com/store/apps/details?id=com.tanvir.messhisab

2. A short demo video. Use the screen recorder built into Android: swipe down for Quick Settings and tap Screen record. Show one real task from start to end, like adding an expense and seeing the totals change. Keep it under a minute. No music needed, and no long intro.

3. A README. The README.md file is the front page of your repo on GitHub. Write it in Markdown: # for a heading, - for a list, and ![text](file.png) for a picture. It says what the app is, shows two screenshots, gives the Play link, and lists what you used to build it.

4. The post. On LinkedIn, write a short story: what problem, who it is for, one thing you learned, the link and the video. In a Facebook group, read the rules first. Many groups allow project posts only on certain days, or not at all. Post once, not in ten groups on the same day.

5. Ask for feedback. Ask a clear question: "What was confusing the first time you opened it?" is better than "How is it?". Put every answer in one list. Fix the most common one first, and ship an update with release notes.

People often post "Please download my app and give 5 stars". That asks for a favour, not feedback. Five stars from friends don't tell you what to fix. Ask people to try it and tell you honestly what they think.

When you read your own README, open it on your phone like a stranger would. Can you tell what the app does in five seconds? Do the pictures load? Does the Play link open the right app?

Words to recognise
READMEMarkdowndemo videoscreen recordingPlay Store linkfeedback
04 / 08

Code tour

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

README.md7 notes
# Mess Hisab
Mentor note · line 1
The app's name as the main heading. One "#" makes the biggest heading in Markdown.
2
Split bazar costs in your mess. Add what you paid, and see who owes what at the end of the month.
4
[Get it on Google Play](https://play.google.com/store/apps/details?id=com.tanvir.messhisab)
· [Watch the 45-second demo](https://youtu.be/your-video-id)
7
![Expense list with totals per member](screenshots/expenses.png)
9![Adding a new expense](screenshots/add-expense.png)
10
11## Features
12- Add an expense in a few taps
13- See the total for each member
14- Works offline. Your data stays on your phone.
15
16## Built with
React Native, Expo, TypeScript, AsyncStorage. Built during Mamun Labs Learn, with reviews from Mamun.
18
19## Feedback
Found something confusing? Open an issue, or write to tanvir.dev@example.com.
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your package is com.tanvir.messhisab. Which link opens your app on Google Play?
  2. 2 / 3Which question gets the most useful feedback?
  3. 3 / 3Your README has ![Home](Screenshots/home.png). The folder in the repo is screenshots. What happens on GitHub?
06 / 08

Explain it back

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

How confident are you with Launch and share?

08 / 08

Done

You can now
Share your app with a working Play link, a one-minute demo and a clear README, and collect feedback you can act on.
Back to Phase 9
On this page
  1. 01Launch and share
  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 live on Google Play. Take a moment. You started with "what does a computer do", and now strangers can install something you made. Now you tell people, in a way that makes them want to try it.

Think of a new fuchka stall. A sign helps, but what brings people is a friend saying "try this one" and showing a photo. Your link, your video and your README are that friend.

1. The Play link. Every app has one, made from its package:

https://play.google.com/store/apps/details?id=com.tanvir.messhisab

2. A short demo video. Use the screen recorder built into Android: swipe down for Quick Settings and tap Screen record. Show one real task from start to end, like adding an expense and seeing the totals change. Keep it under a minute. No music needed, and no long intro.

3. A README. The README.md file is the front page of your repo on GitHub. Write it in Markdown: # for a heading, - for a list, and ![text](file.png) for a picture. It says what the app is, shows two screenshots, gives the Play link, and lists what you used to build it.

4. The post. On LinkedIn, write a short story: what problem, who it is for, one thing you learned, the link and the video. In a Facebook group, read the rules first. Many groups allow project posts only on certain days, or not at all. Post once, not in ten groups on the same day.

5. Ask for feedback. Ask a clear question: "What was confusing the first time you opened it?" is better than "How is it?". Put every answer in one list. Fix the most common one first, and ship an update with release notes.

People often post "Please download my app and give 5 stars". That asks for a favour, not feedback. Five stars from friends don't tell you what to fix. Ask people to try it and tell you honestly what they think.

When you read your own README, open it on your phone like a stranger would. Can you tell what the app does in five seconds? Do the pictures load? Does the Play link open the right app?

Words to recognise
READMEMarkdowndemo videoscreen recordingPlay Store linkfeedback

Your app is live on Google Play. Take a moment. You started with "what does a computer do", and now strangers can install something you made. Now you tell people, in a way that makes them want to try it.

Think of a new fuchka stall. A sign helps, but what brings people is a friend saying "try this one" and showing a photo. Your link, your video and your README are that friend.

1. The Play link. Every app has one, made from its package:

https://play.google.com/store/apps/details?id=com.tanvir.messhisab

2. A short demo video. Use the screen recorder built into Android: swipe down for Quick Settings and tap Screen record. Show one real task from start to end, like adding an expense and seeing the totals change. Keep it under a minute. No music needed, and no long intro.

3. A README. The README.md file is the front page of your repo on GitHub. Write it in Markdown: # for a heading, - for a list, and ![text](file.png) for a picture. It says what the app is, shows two screenshots, gives the Play link, and lists what you used to build it.

4. The post. On LinkedIn, write a short story: what problem, who it is for, one thing you learned, the link and the video. In a Facebook group, read the rules first. Many groups allow project posts only on certain days, or not at all. Post once, not in ten groups on the same day.

5. Ask for feedback. Ask a clear question: "What was confusing the first time you opened it?" is better than "How is it?". Put every answer in one list. Fix the most common one first, and ship an update with release notes.

People often post "Please download my app and give 5 stars". That asks for a favour, not feedback. Five stars from friends don't tell you what to fix. Ask people to try it and tell you honestly what they think.

When you read your own README, open it on your phone like a stranger would. Can you tell what the app does in five seconds? Do the pictures load? Does the Play link open the right app?

Words to recognise
READMEMarkdowndemo videoscreen recordingPlay Store linkfeedback