What makes an app launch different
Most launches follow the same arc: plan, prepare assets, check readiness, announce, follow up. The product launch playbook sets out that arc with roles, phases and readiness gates, and it applies to an app as it does to anything else. Three things about apps change how the arc runs.
The first is the store review. A website goes live when the team publishes it; an app goes live when the store approves it. The listing and the app both have to meet the store's rules, and the app store optimisation guide notes that Apple's App Store Review Guidelines cover the accuracy of metadata, the use of other apps' names and the claims a listing may make, with Google Play's policies covering the same ground. Text that misrepresents the app risks rejection, and the ASO guide's warning holds at launch more than anywhere: the cost of a rejected release is far higher than the cost of a dull subtitle. The plan cannot fix a launch date to the hour without allowing for the review in between.
The second is tracking. The measurement plan for app installs explains that in an app the event specification is part of the product build: it goes through code review, a release and store review, and reaches users only as fast as they update. A launch version that does not record the activation eventThe share of new users or sign-ups who complete the activation event, the action marking first real value, within a set window. cannot report it for weeks, and every campaign that runs on that version runs blind.
The third is the store's own attention. The app marketing hub explains that store features are editorial decisions the stores document as being made on quality, design and newsworthiness, not on request, citing Apple's App Store page for developers. A feature can be welcome; a plan that depends on one has nothing if it does not come. The hub's realistic launch plan is a listing that is ready, a paid campaign tested and paused until launch day, and the business's existing channels pointed at the store at once.
| Row label | A typical product launch | An app launch |
|---|---|---|
| Between finished and live | The team's own publishing step | A store review the team does not control |
| Tracking | Tags can be fixed after launch | Events ship in the build; gaps last until the next release reaches users |
| The page people land on | A page the team designs | A store listing in a fixed template, bound by review rules |
| Free attention | Press, partners, own audience | The same, plus store placements the team cannot request |
| What launch week proves | Interest | Interest, plus how a crowd converts on the listing and behaves in the app |
Readiness before submission
Write the readiness list before the build is submitted, because some of it has to be inside the build. As a phase-gate review would frame it, these are the criteria for the gate between building and launching, agreed in advance and judged honestly.
Events in the build. Following the measurement plan for app installs, specify the install definition, the activation event, the first purchase or core action and the parameters each carries before the launch version is built, and prefer a slightly larger set than seems necessary. Decide which event paid campaigns will optimise to, the optimisation eventThe conversion event an ad set or campaign is told to optimise delivery towards, such as a purchase, lead or install., so it is in the build from day one.
The measurement partner. If paid campaigns are planned, the mobile measurement partnerAn independent service that attributes app installs and in-app events across ad networks. is chosen, its SDKCode a vendor supplies for building into an app, such as an analytics, ad network or measurement partner kit, that records installs and in-app events. is in the build and its links are set up, as the measurement plan and the app install campaign launch checklist require. Write down which tool owns installs, which owns behaviour and which owns cost, before three tools disagree in the first week's report.
The listing. The app store listing checklist covers the title and keywords, screenshots and preview, privacy details, the rating prompt and attribution links. The ASO guide explains the work behind each, from keyword research for store search to screenshots as the conversion asset. Apple's promotional text, the ASO guide notes, can change without a new release, which makes it the place for launch notes that will date quickly.
The review guidelines. Read the current App Store Review Guidelines and Google Play's policies before submission, not after a rejection. Apps in some categories carry extra rules: the entertainment industry guide notes that Apple's guidelines add rules for apps aimed at children and age ratings for all apps.
The first session. New users from launch week are the largest crowd the app will see for a while, so the first session should be ready for them. The guide to app onboarding and permission requests covers the path to first value and when to ask for each permission; asking for everything on the first screen of the launch version spends a crowd's patience at the worst moment.
Building demand before release
The people most likely to install on day one are the ones who already know the business. Before release, the job is to collect them, so that launch day has an audience the team can reach directly, rather than hoping the store supplies one.
A waitlistA list of people who asked to hear when something not yet available can be bought or booked, collected without payment and contacted first. is the simplest tool: a page on the website that explains what the app will do and asks for an email address, linked from the site, from existing emails and from social profiles. The same consent rules apply as for any list, and the wording should say what the person will receive: news of the launch, and anything else only if they choose it. Existing customers of a website or service are the best source, because they already know what the app is for.
Google Ads App campaigns include a pre-registration option alongside installs and engagement, as the app install campaigns guide states from Google Ads Help, for apps that want to build interest on Google Play before release. This guide makes no claims about how pre-registration rewards, notifications or store rules work; Google's own documentation covers them.
Creators and press fit some apps far better than others. For games and entertainment, the entertainment guide treats creator marketing as often the main launch channel, with wishlists or pre-registrations built before launch and creators, press and showcases lined up so coverage lands in the same window, and it reminds teams that creator content must be disclosed. The guide to influencers for app installs covers the links, store listings and per-creator cohorts that let those creators be judged on installs that activate. For a utility or a service app, a short demo for the business's own channels and a note to the press that covers its category may be all that fits. The launch objective sets out the KPIs for a launch window, from launch reach to early adoption, and the channels that suit them.
Budget follows the plan rather than leading it. The marketing budget calculator works back from goals to a budget; for an app, set the goal on activated users rather than installs, and hold part of the paid budget back for after the first cohorts have been read.
Launch week
Launch week is the moment the three levers the app marketing hub describes overlap: store presence, paid installs and the business's own attention. Run it as a sequence, not a single moment.
The listing goes live. Confirm the live listing matches what was approved: text, screenshots, preview and the links that campaigns will use. Check the store pages on both platforms from a device that has never had the app.
Owned channels point at the store. Email the waitlist and existing customers, update the website with links to both stores, post on the business's social profiles, and brief anyone who talks to customers. Send the waitlist first; they asked to hear.
Paid campaigns switch on once the checks pass. The paid campaign should have been built and tested in advance, paused until launch. Switch it on only when the live build is confirmed recording installs and the optimisation event through the measurement partner, and the deep links it uses open the right screens. Start modestly: launch-week traffic from the business's own audience flatters every number, and the cost per installAverage ad cost of each app install. a campaign shows in a week of borrowed enthusiasm is not the cost it will show later.
The rating prompt is wired to a success moment. A new listing with no ratings converts on screenshots alone, so ratings matter from day one. The ASO guide explains that Apple's review guidelines direct developers to use the system rating prompt, and that both stores prohibit incentivising ratings or filtering who is asked by how happy they look; the lever is timing, after a moment of completed value, never at launch and never during an error. The tutorial on app ratings and review replies sets up the prompt and the routine for answering reviews, which matters most in the first weeks when every review is read.
Someone watches the reviews and the crash reports. The first users find problems the test team missed. Reply to reviews that describe them, fix what can be fixed, and use the promotional text to say a fix is coming where a release is needed.
The first month: learning before scaling
The spike a launch produces, the app marketing hub says, is useful mostly for what it teaches about conversion and early retention at volume. Launch-week installs come disproportionately from people who already know the business, and they behave differently from the people paid campaigns and store search will bring later. Scaling spend on launch-week numbers is the most common way an app launch turns into an expensive month. If organic installs keep falling once the launch weeks have passed, the diagnosis of organic app installs falling checks whether the launch peak is being used as the baseline before blaming the listing.
Read the first month by install cohort and by source. For each weekly cohort, track the share who reach the activation event within an agreed window, the share who return in the following weeks, and for paid sources the cost per activated user rather than per install. Compare store conversion by source in the store consoles, keeping in mind that, as the measurement plan for app installs notes, store consoles count downloads by their own rules, so their numbers will not match the partner's or the analytics tool's exactly.
Use a gate before raising spend. The phase-gate method suits this well: write in advance what the first cohorts must show to justify more budget, such as activation and early retention at or above what the plan assumed, and decide at the gate to go on, go with changes, hold while a specific problem is fixed, or stop. A cohort that installs well and activates poorly points at the first session or the promise the listing made, not at the campaign. Fix that before buying more of it.
The first month is also when the listing should start learning. The ASO guide covers the stores' own listing tests, and with real traffic the team can start testing screenshots and text rather than guessing. Keep the waitlist and launch emails going only where they add something; a launch that becomes a fortnight of reminders spends the goodwill the waitlist represented.
A plant care app's launch (illustrative)
Tendrilox Plant Care launches to its waitlist first
Tendrilox Plant Care, an invented plant-care app from a company that already runs a gardening blog, collects 6,400 waitlist sign-ups over 10 weeks from a signup box on its most-read articles. Its readiness gate requires the activation event, "first plant added with a care schedule", to be visible through the measurement partner from the store build; on submission day the event fires in testing but not in the store build, so the team holds its paid campaign, ships a fix, and confirms the event 6 days after launch. Launch day goes to the waitlist by email, then to the blog's newsletter list of 21,000 the next day. Week 1 brings 3,900 installs, 61% of whom add a plant; week 2, with paid social switched on at £150 a day, brings 2,700 installs, 44% of whom add a plant. The team waits for 2 weekly cohorts of paid installs: activation holds at 43% and 46%, and the share of activated paid users who return in their second week is close to the plan's assumption, so it raises the daily budget to £300 at the end of week 4, keeping the optimisation event on plant added rather than install.
The mobile and app marketing guide places the launch in the wider growth loop, and the guide to deciding between an app and the mobile website is the decision that comes before any launch plan.
Common mistakes
- Planning around a store feature. Features are editorial decisions that cannot be requested. Plan on the listing, owned channels and a tested paid campaign.
- Tracking added after launch. Events ship in the build. Specify the activation event and the optimisation event before the launch version is submitted.
- Paid spend before the events are confirmed. A campaign that starts on unconfirmed tracking spends on data that cannot be corrected. Hold it until the live build is verified.
- No audience of its own on launch day. A launch that relies on the store to supply users has no control over its first week. Build a waitlist from the website and existing customers.
- Reading launch week as the future. Installs from people who already know the business flatter every number. Read paid and organic cohorts separately before scaling.
- No rating prompt in the launch version. A new listing needs ratings from the start. Wire the system prompt to a moment of completed value.
- Ignoring the review guidelines until rejection. Read the current guidelines before writing the listing and before submission.
- Scaling on installs instead of activation. Cost per install can look healthy while activation falls. Judge spend on activated users by cohort.
