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

Plan your app

You'll learn to turn your app idea into a one-page plan with one user story, a short list of screens and the data each screen needs.

Why it mattersMost first apps are never finished because the idea grows every week. A small plan is how you actually ship.
about 2 h·needs: Your store listing and release
02 / 08

Watch & read

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

Article
User stories with examples and a templateAtlassian · 10 min · English
MMamun's noteRead "What is in a user story?" and "User story template and examples". It is written for teams, so skip the parts on sprints, story points and Jira. The shape of the sentence is all you need.
ArticleOptional
Problem solvingThe Odin Project · 15 min · English
MMamun's noteRead "Understand the problem", "Plan" and "Divide and conquer". It is about small code problems, but cutting a big app into small pieces works the same way.
ToolOptional
Excalidrawexcalidraw.com · English
MMamun's noteA free whiteboard in the browser, no account needed. Draw your screens as boxes here if paper is not handy. Rough is fine.
03 / 08

Explanation

You have shipped a habit tracker. Now it is your turn to choose the idea. The danger is not a bad idea. The danger is a big one. "Like Foodpanda, but for my campus" has a login, maps, payments, a rider app and an admin panel. That is a year of work for a team.

So you plan a small first version, called an MVP (minimum viable product): the smallest app that is still useful to one real person. Think of a tea stall. It does not open with a full menu. It opens with good tea, and adds singara when people keep asking.

Your plan fits on one page and has four parts.

1. One user story. Who is it for, what do they want to do, and why. This shape is common:

As a student living in a mess,
I want to add what I paid for bazar
so that everyone sees who owes what at the end of the month.

2. The one screen that matters. If your app had only one screen, which one would it be? For this idea, it is the list of expenses with a total per person. Build that first.

3. The list of screens. Write each screen with one line on what it does. Draw each one as boxes on paper, called a wireframe. Four screens or fewer for the first version.

4. The data. For each thing you save, write its fields, like the objects you wrote in JavaScript:

{ id: "e1", who: "Rafi", item: "Rice 5 kg", amount: 450, date: "2026-10-12" }

Then write a "Not now" list. Login, dark mode, charts, sharing: all good ideas, and all later. Writing them down is how you say no without forgetting them.

People often plan the login screen first. A login does not help anyone with their problem, and it is one of the hardest parts to build. Start with the screen that does the main job, saved on the phone like your habit tracker. Add accounts only if the app really cannot work without them.

When you read your own plan, check it like Mamun will: can you say the user story in one breath, does every screen help that story, and do you know where each piece of data is saved?

Words to recognise
MVPuser storyscreen listdata modelscopewireframe
04 / 08

Code tour

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

PLAN.md7 notes
1# Mess Hisab: plan (Tanvir, version 1)
2
For: students who share a mess and buy bazar together.
Mentor note · line 3
Who it is for, in plain words. A real group you know, so you can ask them to test it.
Story: As a mess member, I want to add what I paid for bazar
5so that everyone sees who owes what at the end of the month.
6
The one screen: expense list, with a total for each person.
8
9Screens (version 1)
1. Expenses: list, newest first, total per person at the top
112. Add expense: who paid, item, amount, date
123. Members: add or remove names
13
14Data (saved on the phone)
15member: { id, name }
expense: { id, memberId, item, amount, date }
17
Not now: login, sync between phones, charts, reminders
Done by: 4 weeks. First review with Mamun: end of week 1.
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your idea: a class routine app that shows today's classes and room numbers. Which screen do you build first?
  2. 2 / 3Which one is a user story?
  3. 3 / 3Halfway through, you want to add charts. They are not in your plan. What do you do?
06 / 08

Explain it back

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

How confident are you with Plan your app?

08 / 08

Done

You can now
Write a one-page plan for your own app, cut it down to a first version you can build in four weeks, and say what data it needs.
Next: Build with reviews Back to Phase 9
On this page
  1. 01Plan your app
  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 9Plan your app
01 / 08Overview

Plan your app

You'll learn to turn your app idea into a one-page plan with one user story, a short list of screens and the data each screen needs.

Why it mattersMost first apps are never finished because the idea grows every week. A small plan is how you actually ship.
about 2 h·needs: Your store listing and release
02 / 08

Watch & read

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

Article
User stories with examples and a templateAtlassian · 10 min · English
MMamun's noteRead "What is in a user story?" and "User story template and examples". It is written for teams, so skip the parts on sprints, story points and Jira. The shape of the sentence is all you need.
ArticleOptional
Problem solvingThe Odin Project · 15 min · English
MMamun's noteRead "Understand the problem", "Plan" and "Divide and conquer". It is about small code problems, but cutting a big app into small pieces works the same way.
ToolOptional
Excalidrawexcalidraw.com · English
MMamun's noteA free whiteboard in the browser, no account needed. Draw your screens as boxes here if paper is not handy. Rough is fine.
03 / 08

Explanation

You have shipped a habit tracker. Now it is your turn to choose the idea. The danger is not a bad idea. The danger is a big one. "Like Foodpanda, but for my campus" has a login, maps, payments, a rider app and an admin panel. That is a year of work for a team.

So you plan a small first version, called an MVP (minimum viable product): the smallest app that is still useful to one real person. Think of a tea stall. It does not open with a full menu. It opens with good tea, and adds singara when people keep asking.

Your plan fits on one page and has four parts.

1. One user story. Who is it for, what do they want to do, and why. This shape is common:

As a student living in a mess,
I want to add what I paid for bazar
so that everyone sees who owes what at the end of the month.

2. The one screen that matters. If your app had only one screen, which one would it be? For this idea, it is the list of expenses with a total per person. Build that first.

3. The list of screens. Write each screen with one line on what it does. Draw each one as boxes on paper, called a wireframe. Four screens or fewer for the first version.

4. The data. For each thing you save, write its fields, like the objects you wrote in JavaScript:

{ id: "e1", who: "Rafi", item: "Rice 5 kg", amount: 450, date: "2026-10-12" }

Then write a "Not now" list. Login, dark mode, charts, sharing: all good ideas, and all later. Writing them down is how you say no without forgetting them.

People often plan the login screen first. A login does not help anyone with their problem, and it is one of the hardest parts to build. Start with the screen that does the main job, saved on the phone like your habit tracker. Add accounts only if the app really cannot work without them.

When you read your own plan, check it like Mamun will: can you say the user story in one breath, does every screen help that story, and do you know where each piece of data is saved?

Words to recognise
MVPuser storyscreen listdata modelscopewireframe
04 / 08

Code tour

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

PLAN.md7 notes
1# Mess Hisab: plan (Tanvir, version 1)
2
For: students who share a mess and buy bazar together.
Mentor note · line 3
Who it is for, in plain words. A real group you know, so you can ask them to test it.
Story: As a mess member, I want to add what I paid for bazar
5so that everyone sees who owes what at the end of the month.
6
The one screen: expense list, with a total for each person.
8
9Screens (version 1)
1. Expenses: list, newest first, total per person at the top
112. Add expense: who paid, item, amount, date
123. Members: add or remove names
13
14Data (saved on the phone)
15member: { id, name }
expense: { id, memberId, item, amount, date }
17
Not now: login, sync between phones, charts, reminders
Done by: 4 weeks. First review with Mamun: end of week 1.
05 / 08

Quick check

3 questions. Each one explains itself after you answer.

  1. 1 / 3Your idea: a class routine app that shows today's classes and room numbers. Which screen do you build first?
  2. 2 / 3Which one is a user story?
  3. 3 / 3Halfway through, you want to add charts. They are not in your plan. What do you do?
06 / 08

Explain it back

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

How confident are you with Plan your app?

08 / 08

Done

You can now
Write a one-page plan for your own app, cut it down to a first version you can build in four weeks, and say what data it needs.
Next: Build with reviews Back to Phase 9
On this page
  1. 01Plan your app
  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 shipped a habit tracker. Now it is your turn to choose the idea. The danger is not a bad idea. The danger is a big one. "Like Foodpanda, but for my campus" has a login, maps, payments, a rider app and an admin panel. That is a year of work for a team.

So you plan a small first version, called an MVP (minimum viable product): the smallest app that is still useful to one real person. Think of a tea stall. It does not open with a full menu. It opens with good tea, and adds singara when people keep asking.

Your plan fits on one page and has four parts.

1. One user story. Who is it for, what do they want to do, and why. This shape is common:

As a student living in a mess,
I want to add what I paid for bazar
so that everyone sees who owes what at the end of the month.

2. The one screen that matters. If your app had only one screen, which one would it be? For this idea, it is the list of expenses with a total per person. Build that first.

3. The list of screens. Write each screen with one line on what it does. Draw each one as boxes on paper, called a wireframe. Four screens or fewer for the first version.

4. The data. For each thing you save, write its fields, like the objects you wrote in JavaScript:

{ id: "e1", who: "Rafi", item: "Rice 5 kg", amount: 450, date: "2026-10-12" }

Then write a "Not now" list. Login, dark mode, charts, sharing: all good ideas, and all later. Writing them down is how you say no without forgetting them.

People often plan the login screen first. A login does not help anyone with their problem, and it is one of the hardest parts to build. Start with the screen that does the main job, saved on the phone like your habit tracker. Add accounts only if the app really cannot work without them.

When you read your own plan, check it like Mamun will: can you say the user story in one breath, does every screen help that story, and do you know where each piece of data is saved?

Words to recognise
MVPuser storyscreen listdata modelscopewireframe

You have shipped a habit tracker. Now it is your turn to choose the idea. The danger is not a bad idea. The danger is a big one. "Like Foodpanda, but for my campus" has a login, maps, payments, a rider app and an admin panel. That is a year of work for a team.

So you plan a small first version, called an MVP (minimum viable product): the smallest app that is still useful to one real person. Think of a tea stall. It does not open with a full menu. It opens with good tea, and adds singara when people keep asking.

Your plan fits on one page and has four parts.

1. One user story. Who is it for, what do they want to do, and why. This shape is common:

As a student living in a mess,
I want to add what I paid for bazar
so that everyone sees who owes what at the end of the month.

2. The one screen that matters. If your app had only one screen, which one would it be? For this idea, it is the list of expenses with a total per person. Build that first.

3. The list of screens. Write each screen with one line on what it does. Draw each one as boxes on paper, called a wireframe. Four screens or fewer for the first version.

4. The data. For each thing you save, write its fields, like the objects you wrote in JavaScript:

{ id: "e1", who: "Rafi", item: "Rice 5 kg", amount: 450, date: "2026-10-12" }

Then write a "Not now" list. Login, dark mode, charts, sharing: all good ideas, and all later. Writing them down is how you say no without forgetting them.

People often plan the login screen first. A login does not help anyone with their problem, and it is one of the hardest parts to build. Start with the screen that does the main job, saved on the phone like your habit tracker. Add accounts only if the app really cannot work without them.

When you read your own plan, check it like Mamun will: can you say the user story in one breath, does every screen help that story, and do you know where each piece of data is saved?

Words to recognise
MVPuser storyscreen listdata modelscopewireframe