How Do I Set Realistic Growth Targets for My Mobile App?

Growth targets for mobile apps tend to be set by looking at what feels ambitious rather than what the product can actually support. A team picks a number, 50,000 downloads in the first quarter, 10,000 daily active users by month six, and works backwards from there, treating acquisition as the engine and everything else as a downstream consequence. The problem is that acquisition without retention is a leaking bucket, and spending more on the tap does not help.

Setting a growth target without a retention baseline is like forecasting revenue without knowing your churn rate.

The real question is how many of the people who download your app will still be there in thirty days, and whether your targets account for that drop-off. We work on products where these two things, ambition and reality, are miles apart, and the gap almost always shows up in the same places: onboarding quality, retention mechanics, and a fundamental misreading of what the engagement data is actually saying.

This article walks through how to set targets that reflect how users actually behave, where the standard metrics mislead you, and what the retention data tends to show before things go wrong. The aim is to make your ambitions defensible.

What Makes a Growth Target Realistic in the First Place

A realistic growth target is one that accounts for what your product can sustain, not just what your acquisition budget can generate. That distinction matters because the two numbers are rarely the same, and treating them as equivalent is where most growth plans fall apart.

Sustainable growth requires three things working together. First, enough users entering the product. Second, enough of them staying long enough to experience genuine value. Third, some proportion of them telling others or returning unprompted. If any one of those is broken, the target is built on a false assumption, and no amount of budget adjustment will fix it.

The trap product managers fall into is treating growth as a single-dimension problem. They measure new installs, celebrate when the number goes up, and interpret that as evidence that the strategy is working. But a product that adds 5,000 users a week while losing 4,800 of them within three days is cycling through users at an expensive rate.

Before setting any number, a team needs to know its current day-one retention rate, its day-seven rate, and its day-thirty rate. Those three figures define the shape of real growth. Without them, any target is a guess dressed as a plan.

Why Download Numbers Lie

Download numbers are the most visible metric in mobile app growth, and they are also the least informative. They tell you how many people were curious enough, or persuaded enough, to install your app. They tell you nothing about whether those people found anything worth staying for.

We see teams watch their download numbers grow and read that as product-market fit. The numbers go up, the mood in the room improves, and the next spend is approved. What those teams are often not looking at is retention at day three, day five, and day seven. A rising download curve with a falling retention rate is a product that is getting worse at holding the users it attracts, even as it attracts more of them.

Part of the problem is that downloads feel like a proxy for quality. If people are choosing to install, the reasoning goes, the product must be doing something right. But downloads reflect the quality of your marketing and your app store listing, not the quality of what happens after the tap. The two can diverge significantly, and when they do, the retention data is the honest signal.

Focusing on downloads also creates a specific kind of blind spot. Because the number keeps moving, it feels like progress. The silence from users who have already left, no support tickets, no cancellation reasons, no feedback, is easy to misread as satisfaction. As we see on products we work on, no news is rarely good news in mobile apps. Quiet churn is still churn.

The Retention Cliff: What the Data Actually Shows

The retention drop-off in mobile apps is steeper and faster than almost anyone expects. According to Andrew Chen's analysis of mobile app retention data, around 77% of daily active users stop using an app within the first three days of installation. That is not a marginal attrition rate. That is the majority of your acquired users, gone before the first week is out.

The gap between a well-built product and the average is meaningful, though. On products with genuinely strong onboarding and clear early value, the three-day drop tends to sit in the 40 to 50 per cent range rather than 77 per cent. That 25 to 35 percentage-point difference is entirely attributable to what happens in the first session, not to acquisition quality or spend level.

The retention cliff arrives fast, and product teams are still celebrating downloads when users are already gone.

We worked on a water tracking app and saw a similar pattern. The team had been interpreting user silence as approval, but the retention data told a different story, one that matched the broader industry picture of significant early churn. The top ten personal finance apps, according to Sensor Tower's 2024 data, lose 71% of daily active users between day one and day thirty. That figure is the norm.

The cliff is not inevitable, but treating it as a background condition rather than a design problem is what keeps it in place.

Day One to Day Thirty: Where Growth Targets Collapse

The period between day one and day thirty is where almost every optimistic growth target meets reality. Users who installed with genuine interest leave without explanation. Teams look at their monthly active user numbers and see a figure that feels plausible, without realising how many acquired users it excludes.

Day-one retention is the first honest measure of whether the product delivered on what it promised at the point of acquisition. A rate below 50% after day one is a warning sign. The goal is to push that number as high as possible, and then to hold it through to day thirty, particularly when the team is spending money on user acquisition and needs to justify that spend against actual retained users rather than raw installs.

The gap between installs and actives

The install-to-active gap widens quickly. An app that acquires 10,000 users in its first month might report 2,500 monthly active users and consider that reasonable. But if 7,500 of those users left within the first week, the acquisition cost per retained user is four times higher than the headline figure suggests. Growth targets that ignore this calculation are setting themselves up to spend more than they should to hit a number that means less than they think.

Where the thirty-day figure sits

Day thirty is the threshold that separates users who found a genuine reason to return from those who simply gave the app a chance. Targeting retention at day thirty, rather than just tracking it, changes what gets prioritised in the product. Notifications, habit-forming features, and progressive value disclosure all look different when the goal is thirty-day retention rather than first-session engagement.

How Onboarding Quality Determines Whether Acquisition Compounds

Onboarding is where acquisition either compounds or dissolves. A user who makes it through onboarding with a clear sense of what the product does for them, and who has already experienced at least one moment of genuine value, is far more likely to return. One who exits onboarding confused or underwhelmed is effectively lost, regardless of what the install number says.

The app store listing is part of this. If the listing accurately describes what the product does, the users who download it have already self-selected. They arrive with correct expectations, which means the onboarding experience has less correction to do. When the listing overpromises or describes the product vaguely, users land in a mismatch between what they expected and what they found, and that mismatch shows up directly in early abandonment rates.

Audit your app store listing against the actual first session. If the two are telling different stories, fix the listing before spending more on acquisition. Users who arrive with accurate expectations abandon far less often.

The design of the onboarding flow itself matters too. Asking for permissions, personal data, or account creation before a user has seen any value is a structural friction point. Users who experience friction in their first session are, according to AppsFlyer mobile onboarding studies, 2.7 times less likely to return by day seven. That figure has a direct relationship to acquisition efficiency: the same spend yields significantly fewer retained users when onboarding is poorly sequenced.

What Retention Mechanics Look Like in Practice

Retention does not happen because the product is good. It happens because the product gives users a reason to return that they feel, not just one they can articulate. Those reasons need to be built in deliberately, not hoped for as a consequence of quality.

We worked on an art-based auction game with real money prizes where this played out in clear terms. Initially, we had retention sitting in the mid-sixties to low seventies percentage range. As the quantity of available games declined, usage became sporadic and retention dropped to around 30 to 35 per cent.

The team flagged the problem, but the client's instinct was to add new features rather than address the core content supply issue. It was only when retention hit that low point that the team refocused on restoring the fundamental thing users came for: enough games to play. Retention climbed back to the mid-sixties to low seventies, though rebuilding the trust that had been eroded took considerably longer than fixing the content supply did.

The lesson from that project was that retention mechanics only work when the core reason for using the product is intact. Features added on top of a broken foundation do not compensate for the gap. They add complexity to something that was already failing to hold users.

Before adding a new feature to address a retention problem, check whether the existing core experience is delivering what users originally came for. Feature additions rarely fix a broken foundation.

How Viral Loops Turn Retention Into Acquisition

The most efficient acquisition a product can do is the kind that comes from retained users, because it arrives pre-qualified. A user who joins because a friend invited them, or because the product's natural flow prompted them to share, already has a reason to trust the app before they open it. They convert better and they retain better.

We built this into a travel booking product we worked on, aimed at younger adults in their early twenties to mid-thirties who were booking group trips. We tried the standard post-launch acquisition tactics first: referral discounts, push notifications to re-engage inactive users, social sharing prompts, and email campaigns. None of those moved the retention numbers in a meaningful way.

What actually changed things was a viral loop embedded directly in the booking flow. When someone organised a group trip, the app prompted each individual traveller to download the app to manage communication and submit passport details. One person booking a trip for ten people instantly generated nine new users, each of whom arrived with a clear, immediate reason to engage. Each of those nine could then organise their own trip and repeat the pattern. The loop was built into the product's core function, which meant it ran without any additional acquisition spend.

That kind of loop is only possible when retained users are doing something in the product worth sharing. Retention is the precondition. The viral effect follows from it.

When Features Are Not the Problem

When retention is falling, the default instinct is to add something. A new feature, a redesigned flow, a different notification strategy. The assumption is that users are leaving because the product is not doing enough, and that doing more will bring them back.

Sometimes that is true. More often, the existing features are failing to land, because the product is communicating their value poorly, or because the user has never been guided toward them at the right moment.

We saw this directly on the art-based auction game. The team's first instinct when retention dropped was to propose new feature development. Adding games variety, adding social elements, adding progression systems. The actual cause was simpler and more structural: there were not enough games available to sustain consistent use. No new feature addressed that. The fix was restoring the content that made the product worth opening.

• Check whether users are finding the core features before adding new ones.
• Look at where sessions end: are users leaving before reaching the product's main value?
• Review whether onboarding is surfacing the right features at the right time, rather than burying them in later flows.
• Ask whether the problem is awareness of existing features or dissatisfaction with them.

Feature additions are expensive to build and to maintain. Solving a retention problem with a feature when the real issue is clarity or content supply adds cost without addressing cause.

How to Set Targets That Reflect Real User Behaviour

Setting a target that reflects real user behaviour means starting from your actual retention curve, not from an aspirational install number. The process is sequential, and each step depends on having honest data from the one before it.

1. Establish your current day-one, day-seven, and day-thirty retention rates as a baseline.
2. Set a retention improvement target for each stage before setting an acquisition target.
3. Calculate your effective cost per retained user (not cost per install) at the current retention rate.
4. Model what the acquisition number needs to be to yield your target active user base, given realistic retention.
5. Revisit and revise the model at thirty-day intervals as real data comes in.

This approach produces a target that is tied to the product's demonstrated capacity to hold users, rather than one that assumes retention will improve as a byproduct of scale. Scale does not improve retention. Better onboarding, better mechanics, and better core value delivery do.

A growth target built this way is also easier to defend to stakeholders, because it is based on a chain of observable metrics rather than a single optimistic number. When something in the chain underperforms, it is immediately visible where, and the response can be targeted rather than general.

What to Measure and When to Be Worried

The metrics that appear most often in product reviews, session length, daily active users, monthly active users, are not the most informative ones. They describe activity, but they do not explain it. A user spending twelve minutes in an app could be deeply engaged with the core feature, or could be stuck in a loop they cannot exit. The session length looks the same in both cases.

These are what we call vanity metrics. They look impressive in a deck and they feel like evidence of health, but they tell you nothing about whether users are getting real value from the product or simply being kept there by friction they cannot navigate around. The question they fail to answer is why the user stayed, and that question is the one that matters for retention.

Track the percentage of users who complete your core action in their first session alongside session length. A high session-length average with a low core-action completion rate usually means users are confused, not engaged.

The signals that matter more

Day-three retention, day-seven retention, and day-thirty retention are the three numbers worth watching most closely. Alongside those, track the completion rate of your onboarding flow and the percentage of first-session users who reach the product's primary value moment. If a large proportion of users are dropping before that moment, the onboarding is the problem regardless of what the session-length average says.

When to treat silence as a warning

Absent user feedback is not a sign that the product is working. Users who abandon rarely say why. They do not file support tickets or send cancellation emails. They simply stop opening the app, and if the team is only watching active-user counts rather than churn rates, that departure goes unnoticed until the aggregate number drops far enough to be visible. Proactive retention tracking, rather than reactive response to complaints, is what catches problems early enough to address them.

Conclusion

Growth targets for mobile apps are only useful if they are tied to the metrics that reflect how the product actually performs, rather than the ones that look best in a presentation. Downloads measure interest. Retention measures value. The two are related, but they are not the same thing, and building a growth strategy on download numbers while ignoring the retention curve is a reliable way to spend a lot of money on users who are already gone.

The products that sustain real growth are the ones where the onboarding delivers a genuine first-session experience, where the core reason to return is maintained rather than diluted by feature additions, and where acquisition is structured to compound through retained users rather than to replace churned ones at continuous cost.

The art-based auction game dropping from the low seventies to 35 per cent retention because content supply was not maintained, the travel app finding its most efficient acquisition inside the booking flow itself, the water tracking app discovering that user silence had been masking significant early churn, these are all the same story told in different contexts. The retention curve is the honest signal. Everything else is noise until you know what it says.

If you are setting growth targets for a mobile product and want to make sure they are built on the right foundations, let's talk about your app's retention strategy.

Frequently Asked Questions