Back to Blog

Why your app retention sucks (and how to fix it)

I had a founder come to me last year absolutely buzzing. 10,000 downloads in the first week. Paid acquisition was humming. The numbers looked incredible on paper.

Two months later, the app had 47 daily active users. Out of 10,000. That's a 99.5% drop-off. Ten grand in marketing spend, essentially flushed.

This happens all the time. Founders obsess over acquisition. How many downloads, what's the CPI, how do we get more installs. Meanwhile, the bucket has a hole the size of a basketball and they're trying to fill it with a garden hose.

Retention is the game. Everything else is a vanity metric until you've figured out how to keep people coming back.


The benchmarks you need to know

Before you can fix retention, you need to know what good looks like. Here are the industry benchmarks across consumer apps, pulled from data by Adjust, AppsFlyer, and Mixpanel:

Day 1 retention (users who come back the day after install):

  • Average across all apps: 25-27%
  • Good: 35-40%
  • Great: 45%+
  • Gaming apps average: 28%
  • Health & fitness apps: 22%
  • Social apps: 30%

Day 7 retention:

  • Average: 11-13%
  • Good: 18-20%
  • Great: 25%+

Day 30 retention:

  • Average: 5-6%
  • Good: 10-12%
  • Great: 15%+

If you're below average on any of these, you have a retention problem. If you're above "great," you have something genuinely special. Most apps we see for the first time sit somewhere between "terrible" and "average."

The brutal maths: if you have 25% Day 1, 12% Day 7, and 6% Day 30, then for every 1,000 users you acquire, only 60 are still using your app a month later. You need to acquire 17 users to keep one. At $3-5 cost per install in Australia, that's $50-85 per retained user. For most consumer apps, the economics simply don't work unless you fix the retention curve.


Why users leave on day one

The first session decides everything. If a user doesn't experience value in the first 2-3 minutes, they're gone. Not "maybe gone." Gone. They'll never open your app again.

The most common day-one killers:

Forced account creation before value

You open the app for the first time and immediately hit a signup wall. Name, email, password, confirm password, verify email. You haven't seen a single screen of the actual product yet.

Every field in your signup form costs you users. Literally. Each additional field drops conversion by 10-15%. If you're asking for six fields before showing value, you've lost half your users before they've started.

The fix: let people explore first. Show them the core experience. Let them do something. Then ask for the account when they want to save their progress or unlock more features. Apple's "Sign in with Apple" and Google's one-tap sign-in exist for exactly this reason. Use them.

Onboarding that teaches instead of activates

Nobody reads tutorial screens. I know you spent hours writing those five swipeable cards explaining every feature. Nobody reads them. Users skip them immediately. The ones who don't skip them forget everything by the time they reach the main screen.

Good onboarding doesn't explain the app. It gets the user to their first meaningful action as fast as possible. Duolingo doesn't explain how language learning works. It throws you into a lesson in the first 30 seconds. You're learning before you even realise the onboarding is happening.

Ask yourself: what is the single most valuable thing my app does? Now, how fast can a new user experience that thing? If the answer is more than 60 seconds, you have work to do.

Too many choices too early

New users don't know your app. They don't know what to tap. If you dump them on a home screen with 8 tabs and 15 features, they freeze. Choice paralysis is real and it kills activation.

The best consumer apps are ruthlessly focused in the first session. One clear path. One thing to do. One win to achieve. Expand from there.


The day 7 problem: no reason to come back

Day 1 retention is about first impressions. Day 7 is about habit formation. And habits don't form on their own. You have to engineer them.

Nir Eyal's Hook Model is genuinely useful here. The cycle is: trigger, action, variable reward, investment. Let me break that down into practical terms.

Triggers need to be external first

Before your app becomes a habit, users won't think to open it. You need to remind them. Push notifications are the most powerful tool you have for this, and most founders completely botch them.

Bad push notifications:

  • "Hey! You haven't opened AppName in a while!" (desperate)
  • "Check out our new features!" (nobody cares)
  • "Don't miss out!" (miss out on what?)

Good push notifications:

  • "Your weekly report is ready. You walked 23% more than last week." (personal, specific, valuable)
  • "Sarah just commented on your post." (social trigger, curiosity)
  • "Your 5-minute meditation streak is at risk. Tap to keep it alive." (loss aversion, investment protection)

The difference is value. Every notification should give the user a reason to tap that benefits them, not you. If your notification is about your app's needs rather than the user's needs, don't send it.

Timing matters too. Analyse when your active users typically open the app and send notifications in that window. A fitness app notification at 6am works. At 11pm, it's annoying. Most analytics tools, including tools we recommend in our dev process guide, will show you these usage patterns.

Variable rewards keep people curious

If your app delivers the exact same experience every time, it becomes predictable. Predictable is boring. Boring gets deleted.

Variable rewards don't need to be complicated. A social feed that shows different content each time. A fitness app that gives you a new challenge. A learning app that adapts to what you got wrong yesterday. Even small amounts of unpredictability keep the brain engaged.

Investment creates switching costs

Every time a user puts something into your app, they're building switching costs. Data, preferences, history, social connections, streaks, saved content. The more they invest, the harder it is to leave.

This is why Spotify gets stickier over time. Your playlists, your listening history, your Discover Weekly algorithm. It knows you. Starting fresh on another platform means losing all of that.

Design for investment early. Ask users to customise something. Let them set preferences. Get them to create content, even if it's just a saved favourite. Every investment makes the next visit more likely.


The day 30 cliff: where real retention lives

If you can get someone to Day 30, you've likely got them for months. The retention curve flattens after 30 days. The users who survive that long have formed a genuine habit.

But getting there requires sustained value delivery. Here's what works:

Progressive disclosure of features

Don't show everything on day one. Reveal new features as users mature. Week 1: core features only. Week 2: introduce advanced options. Week 3: unlock power-user tools. This keeps the experience fresh and gives users something new to discover.

Strava does this brilliantly. New users see basic tracking and a feed. As they use it more, segments appear, challenges unlock, training plans become relevant. The app grows with the user.

Streaks and loss aversion

Humans are twice as motivated by avoiding a loss as they are by pursuing a gain. Streaks exploit this perfectly. Once someone has a 14-day streak, the pain of breaking it is real. Duolingo's entire retention strategy is built on this.

But be careful. If your streak mechanic punishes people for missing one day with no recovery option, you'll create resentment. Duolingo added "streak freezes" for exactly this reason. Let people protect their investment.

Community and social features

If you can make your app social, retention goes up dramatically. Users who connect with at least one other person in an app have 2-3x higher retention than solo users. People don't just come back for the product. They come back for the people.

This doesn't mean you need to build a full social network. Even lightweight social features work. Leaderboards, shared challenges, the ability to follow friends, comment threads. Anything that creates a reason to check in that goes beyond the core utility.


How to actually diagnose your retention problem

Before you start fixing things, figure out where users are dropping off. Open your analytics and look at the retention curve. Where's the steepest drop?

  • Steep drop Day 0 to Day 1: Your onboarding or first session is broken. Users aren't finding value fast enough.
  • Steep drop Day 1 to Day 7: You're not giving users a reason to come back. Your trigger system (notifications, emails) is weak or your core loop isn't engaging enough.
  • Steep drop Day 7 to Day 30: The novelty has worn off and you haven't created enough depth. Users need progressive value, community, or investment mechanics to stay engaged.
  • Gradual decline across all periods: You might have a product-market fit problem. If nobody's sticking around, the product might not be solving a painful enough problem. Go back to validation basics.

Run cohort analysis. Don't look at overall retention numbers. Break it down by acquisition channel, by user behaviour in the first session, by feature usage. You'll almost always find that users who complete a specific action in the first session retain at 2-3x the rate of those who don't. That action is your activation metric. Optimise everything around getting new users to complete it.


The one thing most founders get wrong

They try to fix retention with features. "If we just add this one more thing, people will come back." No. Adding features to an app with bad retention is like renovating a house with a cracked foundation. More features just give churned users more things to ignore.

Fix the core loop first. Make the primary experience so good that people want to come back for it. Then layer on engagement mechanics. Then add features. In that order.

Retention isn't a feature problem. It's a value-delivery problem. Are you delivering value fast enough in the first session? Are you reminding users of that value through intelligent triggers? Are you deepening the value over time so the app becomes harder to live without?

Get those three things right and retention takes care of itself. Get them wrong and no amount of push notifications or gamification will save you.

If your retention numbers are underwater and you're not sure where to start, book a game plan call and we'll look at the data together. Sometimes a fresh set of eyes is all it takes to spot the leak.

Jarrod Macfarlane
Jarrod Macfarlane
Founder, Rebelled

Ready to build your app?

We'll help you figure out if your idea has legs, design it properly, and get it live.

Get Your Free Game Plan