Mobile app marketing: getting the first 1,000 real installs

Most app launches we have been brought into had already spent the budget on installs before anyone checked whether people kept the app. This is the sequence we use instead, in order, for a new app with a modest budget.

Fix the store listing before anything else

Every channel you use, organic search in the store, paid campaigns, a link from your website, passes through the store listing. Its conversion rate multiplies everything else you do.

The elements that matter, roughly in order: the first screenshot, the title and subtitle, the icon, and the first three lines of the description. Almost nobody reads past those.

Write the subtitle for search terms someone would actually type, not for a slogan. Make the first two screenshots show the app doing the thing, with a caption explaining what is being looked at, rather than a phone floating on a gradient. Test the icon against competitors at real size on a real device, not at 512 pixels in a design tool.

Store search still drives a large share of discovery, and both stores index the title and subtitle heavily. Those fields are the highest-value text you will write all year.

Get the first 200 installs from humans

Before any paid acquisition, put the app in front of people you can have a conversation with: existing customers, an email list, a community you are genuinely part of, colleagues, a beta group.

The point is not the install count. It is that these people will tell you why they stopped using it, which no dashboard will. Every serious problem in the apps we have worked on was findable in the first fifty conversations.

Use a staged rollout, watch the crash rate, and fix onboarding before you widen distribution.

Watch retention, not installs

The number that decides whether to spend money is day-7 retention: of the people who installed on a given day, how many opened the app a week later.

Benchmarks vary enormously by category, so compare against your own trend rather than an industry average. The logic is universal. If day-7 retention is very low, paid acquisition converts budget into uninstalls at a fixed exchange rate. Fixing retention first is not a delay, it is the thing that makes the spending rational.

The usual causes of poor early retention: onboarding that asks for permissions or an account before showing any value, a core action that takes too many steps, and a value proposition the store listing promised but the app does not deliver in the first session.

Then, and only then, buy installs

When retention is acceptable, paid acquisition becomes worthwhile. Start narrow: one platform, one country, one audience, a small daily budget, creative that shows the app in use.

Measure cost per retained user, not cost per install. An install at $0.80 that churns in two days is more expensive than one at $3 that stays.

Track properly. Attribution on mobile has become considerably harder with platform privacy changes, so use an attribution provider, expect gaps, and reconcile against in-app events you control. Expect the numbers to disagree; decide in advance which source you will act on.

Build a review habit into the product

Ratings drive both store ranking and listing conversion, and they compound. The pattern that works: prompt after a successful action, the third completed task, the first shared result. Never on first launch, and never after an error.

Route unhappy responses into a support conversation before the store prompt. That is not gating a review, which is against the rules; it is choosing when to ask. Reply to reviews, especially the bad ones, because prospective users read the replies before they read the app description.

Give the app a website

Apps that exist only inside a store are invisible to search engines. A small site with a page describing the app, a support page, a privacy policy and a blog covering the problem the app solves will pick up search traffic the store never will, and gives you somewhere to send press and partners.

It also gives you deep links, which improve the experience for anyone arriving from your own emails and campaigns. A page or two is enough; this is not a web development project unless you want it to be.

What we would not spend on at launch

Press releases, which nobody reads. Paid review services, which are against store rules and detectable. Incentivised installs, which destroy your retention data. Large-scale user acquisition before retention is proven. And a launch video costing more than the first quarter's ad spend.

A realistic ninety days

Weeks one to two: store listing, analytics, crash reporting, review prompt. Weeks three to six: the first 200 installs from people you can talk to, and fix what they tell you. Weeks seven to ten: measure retention honestly and iterate onboarding. Weeks eleven to thirteen: if retention holds, run a small paid campaign in one market and measure cost per retained user.

That sequence costs less than most launch campaigns and it ends in a decision you can act on.

When to get help

The listing work is worth doing with someone who has written a few, because it is cheap, it multiplies everything downstream, and it is hard to judge your own icon. Paid acquisition is worth handing over once the daily budget passes the point where a bad week matters. That split is how our app store optimisation and mobile advertising engagements usually start, and if the app itself is not built yet, the build decision comes first: Flutter, React Native or native.