Skip to content
Learning Centre · Launch & Growth

App Launch and Growth

Launching an app is not the end of the build process. It is the beginning of the product process. Everything founders need to know about launching an app and growing a user base, from App Store submission to the metrics that actually matter.

Where launch really starts

What an app launch actually involves.

Many founders think launching an app means submitting it to the App Store. That is one step in a longer process. The decisions made in the weeks before submission determine the quality of the feedback available afterwards, and the feedback is what tells you whether the product is working.

The App Store submission process itself is straightforward once you know it. Apple typically reviews in 24 to 48 hours, sometimes longer. Google is faster, a few hours to a few days. Both can reject and require resubmission for reasons ranging from metadata issues to genuine policy breaches, so plan for at least one round of revisions in your launch timeline.

A soft launch matters more than most founders realise. A full launch commits marketing spend and PR attention to a product before you know how real users behave in it. A soft launch tests that behaviour at small scale first, in a limited market or to a limited audience, so the data you gather is representative and the mistakes you find are cheap to fix.

The soft launch is where you learn whether onboarding works, whether the crash rate is acceptable, whether users do the thing the product is designed for and whether they come back. Only when those signals are in a reasonable range does full launch make sense. Launching to everyone on day one is rarely the right decision. It converts a controllable experiment into an uncontrollable one.

Before either launch, there is a checklist you cannot skip. Onboarding tested end to end. Analytics set up and firing correctly. Crash reporting active with a route for the team to see and act on it. A customer support pathway in place, even if it is one person answering emails. Miss any of these and you are launching blind.

01
Onboarding tested end to end with real users, not just the team who built it.
02
Analytics installed, firing correctly, and mapped to the events that actually matter.
03
Crash reporting active with a clear route for the team to see and respond.
04
Customer support pathway in place, even if it is one person answering emails.
05
Soft launch plan defined, with success criteria set before the launch, not after.

Not sure if your app is ready to launch?

A Feel Factor audit will tell you exactly where the experience is falling short before your users find out.

Book an audit →
Most apps are launched before they are ready and grown without a strategy. The work you do before day one decides the quality of the data you have on day two.
App Store Optimisation

ASO is a discipline. Treat it like one.

App Store Optimisation is not decoration for a listing. It is the single largest lever on organic discoverability, and it works whether or not you are running paid acquisition. Done well, it makes every marketing pound go further. Done badly, it caps the ceiling of everything else.

ASO covers everything the stores use to rank and display your app: title, subtitle, keyword field on iOS, description, screenshots, preview video, category, ratings and reviews. Each element does a different job. Title and subtitle carry the most weight for ranking. Screenshots and preview video carry the most weight for conversion. Most users decide whether to download before they read a single word of the description, so the visual assets are doing the real work.

Screenshots should not be marketing posters. They should communicate, in the first two frames, what the product is and who it is for. Preview videos need to work with sound off, because most people watch them that way. Category selection matters more than founders expect. Picking a competitive category where you have no realistic chance of ranking is worse than picking a smaller category where you can be visible.

Ratings and reviews affect both ranking and conversion, and they compound. A product with a 4.6 average and 800 reviews is not just rated higher than one with 3.9 and 40 reviews, it is trusted more, ranks better, and converts a higher percentage of the traffic it sees. Building a review-request moment into the product, timed to a point where the user has just had a positive experience, is one of the highest-leverage things you can do.

ASO is not a one-time task. Store algorithms change, competitors update their listings, seasonal search terms shift. Review your ASO performance on a regular cadence and update accordingly. What ranked in month one will not rank in month six unless you keep working on it.

Ranking

Title & subtitle

The heaviest-weighted fields for search. Include your primary keyword naturally, not stuffed.

Conversion

Screenshots

The first two frames do the work. Communicate what the product is and who it is for.

Conversion

Preview video

Design it to work with sound off. That is how most people will watch it.

Discovery

Category

A smaller category where you can be visible beats a large one where you cannot.

Trust

Ratings & reviews

They affect both ranking and conversion. Ask at a moment the user has just had a good experience.

Ongoing

Review cadence

ASO is not one-and-done. Review performance monthly and update based on data.

Launch marketing strategy

Get the first users. Then earn the next ones.

Launch marketing works when it matches the state of the product. Paid acquisition spent on an app that does not retain is money burned. The right sequence is retention first, then organic, then paid.

A waitlist or pre-launch audience is the most valuable asset you can build in the weeks before launch. Even a modest list of people who have opted in and are actively waiting gives you day-one momentum: initial downloads, initial ratings, early word of mouth. Without that base, day one is quiet, and a quiet day one makes it harder to build momentum in weeks two and three.

Organic channels do the heavy lifting at launch. Social media, PR, content and community are slower to build but they compound. They reach people who trust the source, which means the users you acquire are more likely to be genuinely interested in the product, and more likely to stay. Paid acquisition is different. It scales, but only after retention is working. Spending on paid acquisition before you know that new users stick is the fastest way to lose money in app marketing.

Word of mouth is the most valuable growth channel there is, because acquired users cost nothing and arrive pre-trusted. You design for it by building moments into the product that people naturally want to share, and by making sharing a first-class action rather than a buried setting. A referral mechanism supports word of mouth but does not replace it. If the product is not worth talking about, no referral scheme will fix that.

Launch partnerships work when they are genuinely aligned. A complementary product, an engaged community, a credible individual voice. Alignment matters more than reach. A small partnership with the right audience delivers more real users than a large partnership with the wrong one.

Not sure if your app is ready to launch?

A Feel Factor audit identifies exactly where the experience falls short before it becomes a poor rating.

Book an audit →
The metrics that actually matter

Downloads are a vanity metric. Retention is the measure of product success.

The number of downloads on day one tells you very little about whether the product is working. The number of users still opening it on day seven tells you almost everything.

Retention is measured in cohorts. Day 1, Day 7 and Day 30 are the standard checkpoints, and each says something different. Day 1 tells you whether onboarding worked. Day 7 tells you whether the product delivered on its promise. Day 30 tells you whether it has become a habit. If any of the three is low, the fix sits in a different part of the product.

Session length and session frequency matter alongside retention. High retention with very short sessions can mean the product opens but the user never really engages. Low frequency with long sessions can mean the product is used but not habitually. Read the two together, in the context of what the product is designed to do.

Churn is the same data seen from the other side. The headline churn number is useful, but the interesting question is why. Churn from a specific screen points to a UX problem. Churn at a specific moment in the lifecycle points to an expectations problem. Churn across the board points to a product-market fit problem. All three need different responses.

Net Promoter Score and open-ended qualitative feedback fill in what the numbers cannot say. Analytics tells you what happened. Users tell you why. Both are needed. Setting up the analytics stack properly before launch, so the data is clean from day one, is not optional. Retrofitting analytics after launch always loses the earliest, most informative data.

Retention benchmarks worth knowing

Metric What most apps see What good looks like What it tells you
Day 1 retention 25% 40%+ Did onboarding land? Did the user find the thing the product is for?
Day 7 retention 11% 20%+ Did the product deliver on the promise the store listing made?
Day 30 retention 4% 10%+ Has the product become a habit? Is there anything to compound?
Session frequency Varies by category In line with product intent Is the user doing what the product is designed for?
Growth after launch

Growth is a retention problem before it is an acquisition problem.

Acquiring users who leave in the first week does not build a product. It builds a leaky bucket. Understand why users leave, design the product to prevent it, and only then pour more in the top.

Retention is the foundation of growth because retention compounds. A product where 40% of new users are still active on Day 30 grows on its own base. A product where 4% are still active on Day 30 has to keep buying its audience back every month, and the economics of that rarely work. This is why the sensible sequence is retention first, then organic loops, then paid.

Successful apps design for a growth loop rather than relying on paid acquisition alone. A growth loop is a mechanism where the product’s own use generates the next user. Word of mouth is one loop, virality is another, habit is a third. Each requires the loop to be designed into the product deliberately. Viral features work when sharing is a natural part of the experience, not a bolted-on ask.

Post-launch data is only useful if you use it to change the product. Most teams read the data, discuss the data, and then keep marketing the same product harder. The teams that actually grow use post-launch data to iterate on the product itself. That is where retention improves. That is where the loop starts to work.

Retention problems after launch trace back to onboarding and UX in most cases. If Day 1 retention is weak, onboarding is not doing its job. If Day 7 is weak, the product’s core value is not landing. Diagnosing which is a UX exercise, not a marketing one. Paid acquisition, when it comes, comes last. Once retention is holding, paid becomes a way to accelerate a system that already works. Before that, it is a way to waste money.

The growth sequence, in order

01 · Retention working
First
02 · Organic loop designed
Second
03 · Product iteration on data
Ongoing
04 · Paid acquisition
Last

Low retention after launch usually points to onboarding and UX problems.

A Feel Factor audit identifies exactly where the experience is falling short and what to fix first.

Book an audit →
Frequently asked questions

Common questions about how to launch an app.

How long does App Store review take?

Apple is typically 24 to 48 hours, sometimes longer. Google is typically a few hours to a few days. Both stores can reject and require resubmission for reasons ranging from metadata issues to genuine policy breaches. Plan for at least one round of revisions in your launch timeline, and do not schedule launch marketing to a date you cannot move.

Should I launch on iOS or Android first?

The answer depends on where your audience actually is, what you are testing, and the technical shape of your product. Read our comparison in App Store vs Google Play: Which Is Right for Your App? for the full breakdown.

What is a soft launch and do I need one?

A soft launch is a limited release, usually to a smaller market or a controlled audience, before the full public launch. It tests real user behaviour at a scale where the mistakes you find are cheap to fix. Most products benefit from one. It tells you whether onboarding works, whether crash rates are acceptable, whether users do the thing the product is designed for, and whether they return. Only when those signals look reasonable is a full launch a sensible next step.

How do I get my first users?

A pre-launch waitlist, organic channels like PR and community, and well-chosen partnerships do most of the work at the start. Paid acquisition comes later, once retention is working. We cover the practical options in 10 Effective Marketing Tactics for Your Mobile App Launch.