Blog

My users don't come back: retention basics for student builders

· buildtolaunch

You launched, people signed up, and then most of them never opened your app again. This guide is for students who built their first product and want to understand why users leave and what to try next. You get a simple way to measure it, five common causes, and a plan for the next two weeks. It is one step in the student launch playbook.

Short answer

Retention means the share of your users who come back after their first visit. Measure it by grouping people by the day they first used your app, then checking how many return on day 1, day 7 and day 30. If few come back, talk to five of the people who left, make the first minute deliver one clear result, and give them a reason to return. Fix one thing at a time.

What retention is (and the words around it)

Three terms you will see in analytics tools:

  • Cohort: a group of users who started in the same period, for example everyone who first opened your app this week.
  • Retention: the percentage of a cohort that comes back in a later period. If 20 people started on Monday and 5 opened the app again a week later, week-1 retention for that cohort is 25%.
  • Activation: the moment a new user gets the first real value, such as saving a first note or sending a first message. Users who never get that first value have little reason to return.

PostHog, a free analytics tool, describes its retention view as having a start event that defines the cohort and a return event that decides whether the user was retained. The first period always reads 100% because everyone in the cohort did the start event. Google Analytics 4 has a Retention overview report that shows how users acquired on each day return and engage at Day 1, Day 7 and Day 30 (both checked 18 Nov 2026).

How to measure it by hand (no tool needed)

You can do this in a spreadsheet when you have fewer than a few hundred users.

  1. List every user and the date they first used the app.
  2. Add a second column: did they use it again at least once, 7 or more days after the first time?
  3. Count the yes answers and divide by the total.

A made-up example, for illustration only: 40 people tried your study-planner app in its first week. 6 opened it again between day 7 and day 14. That is 6 of 40, or 15% week-1 retention. Now you have a number to improve, even if it looks small.

Do not compare your number with big-company benchmarks. Your app has a handful of users and a different purpose. Compare this week with last week.

Set up a free tool

If you want automatic charts, pick one:

  • PostHog: its free plan includes 1 million product-analytics events a month and 5,000 session recordings, and no credit card is needed (checked 18 Nov 2026). Its retention insight shows each cohort and the share that returned in later periods.
  • Google Analytics 4: its Retention overview report covers new vs returning users and Day 1, 7 and 30 retention by cohort.

For a simple weekly tracking table, see measuring after launch (in Vietnamese). Note what the tool cannot tell you: it shows that users left, not why.

Why users do not come back: 5 causes

1. They never reached the first result

The most common cause. A user signs up, sees an empty screen and leaves. Watch two people use your app for the first time without helping them. Where do they stop?

Try: cut steps before the first result. Pre-fill with sample data. Make the first screen offer one clear action.

2. The app solves a one-time problem

Some apps are used once: a tool to pick a semester course, a one-off calculator. People are not leaving because the app is bad. They have no reason to return.

Try: decide honestly whether your use case repeats weekly, monthly or never. If never, change the goal: count referrals or completed tasks, not returns.

3. Nothing reminds them

People forget small apps, and they have a lot of apps already.

Try: an email or message when something new happens for them, or a weekly summary. Ask for contact details only after the user has seen value.

4. The result was not good enough

Maybe the app works but the output is only so-so.

Try: read what the first-time users produced. If the results are poor, improve the core before adding features.

5. You are reaching the wrong people

If people join from a random post and are not the ones with the problem, they will not return.

Try: compare retention for users from different sources. Double down on the group that returns. See the first 100 users.

Talk to the people who left

Numbers show that users leave. Conversations show why. Message five people who used the app once and did not return. Use a short, friendly message:

Hi [name], thanks for trying [app]. I'm a student building it and I'm trying to make it better. Could I ask you 3 quick questions about why you stopped? It would take 5 minutes, and I'm happy to share what I learn.

Questions to ask: What were you hoping to do? What happened? What do you use instead? The Vietnamese guide 5 questions to ask users after launch has a fuller list.

A two-week plan

DayAction
1Count cohorts and week-1 retention in a spreadsheet
2 to 3Watch 3 new users try the app; note where they stop
4 to 5Message 5 users who left; write down their answers
6 to 8Fix the single biggest blocker before the first result
9 to 10Add one reminder (email or message) tied to something useful
11 to 14Re-measure with the next week's cohort and compare

Change one thing at a time. If you change five things, you will not know what worked. A weekly rhythm makes this easier; see why shipping every week beats one big launch. If almost no one has arrived at all, read I launched and nobody came first.

Practise on buildtolaunch

buildtolaunch is a free community for university students in Vietnam and Southeast Asia, any major, no coding needed to start. Post your update on the Launch League each week, so you have a reason to ship a fix and a place to ask for feedback. The courses library has 70+ free courses, and Spaces let you build with an AI teammate. Sign up to start.

FAQ

What is a good retention rate for a student project?

There is no single number that applies to every app. A study app used before exams and a daily habit app should not be compared. Measure your own week-1 retention, then try to raise it a little each week. If a few real users keep coming back, that is a better sign than a big number from a tiny group.

What is the difference between retention and engagement?

Retention asks whether a user came back. Engagement asks what they did while they were there. PostHog notes that a retention insight shows whether users returned, not how often, and recommends a stickiness insight for frequency.

How many users do I need before retention means anything?

You can start with 10 to 20 users, but treat the number as a hint. With small groups, one person changes the percentage a lot. Combine the number with conversations.

Should I add notifications or emails?

Only after the first-use experience is good. A reminder cannot fix an app that gave the user nothing on day one. When you add one, make it useful, such as a result that is ready, not a generic "we miss you".

My app is a one-time tool. Is low retention a problem?

Not necessarily. For a one-time tool, track whether people finish the task and whether they tell someone else about it. Decide what "success" means for your use case before you chase returns.

What if users come back once and then stop?

Look at what happened in that second visit. Often the user looked for something that was not there. Ask them directly, and check what they did on the first and second visits.

Back to the plan: read the full guide.