How to Launch an App: The Sequence That Ships on Time
Launching an app is a sequence problem, not an engineering one. The code is usually ready weeks before the account verification, the store metadata, the billing plumbing and the review round trip are. Get the order right and launch day is uneventful. Get it wrong and a finished build sits idle while you wait on a form.
Don't pay full price to build this.All 49 App Development tools below come with a discount code, a startup programme or free credits.Claim these perks →
Open the developer accounts before you write the last feature
Both stores charge for the right to publish and both verify you before they let you. Apple's programme runs on an annual fee and, for a company account, a legal entity check that can stall for weeks if your registration details do not match your bank records. Google charges once, verifies faster, and demands a confirmed address and phone number before anything goes live.
Open both accounts the week you commit to shipping, not the week you feel ready. An account stuck in verification is the single most common reason a finished build sits on a laptop. Enrol as the entity you actually intend to trade under, because switching the account holder later means a new listing and the loss of every rating attached to the old one.
While you wait, finish the boring parts. Both stores hold payouts until you have completed tax forms and attached a bank account whose name matches the account holder. Set up signing certificates and provisioning early, back the keys up somewhere that is not one developer's laptop, and register the bundle identifier you want before somebody else claims it.
Build the release pipeline before you need it
Your first build should reach a tester through the same pipeline that will later reach a customer. On Apple that means TestFlight, on Google an internal testing track. Both involve a real upload, real processing time and, for external testers, a real review. Discovering that pipeline during launch week is how a date slips by a fortnight.
Automate the upload. Manual archive-and-submit works right up until the day it does not, and it always fails at the worst possible moment. A pipeline that builds, signs, uploads and notifies on every merge to your release branch turns shipping into a decision rather than an afternoon of clicking through dialogue boxes.
Recruit external testers earlier than feels comfortable. Internal testers share your assumptions and often your device model. External testers find the onboarding dead end, the permission prompt that reads like a threat, and the crash that only occurs on a phone with almost no free storage left.
Store review is a policy check, not a quality bar
Rejections cluster in a small number of places. Functionality that is unreachable behind a login, a demo account that does not work, missing or incomplete privacy declarations, subscription screens that fail to state the terms plainly, and any purchase path that routes around the store's own billing for digital goods.
Give the reviewer a working demo account, a note explaining anything gated or unusual, and a short video if the feature needs hardware you cannot assume they have. Most rejections are resolved by a reply in the resolution centre rather than a rebuild, and that conversation is far faster than resubmitting blind and hoping.
Budget for at least one rejection. First submissions are scrutinised harder than updates, and each round trip costs days rather than hours. Teams that announce a launch date and then submit the day before are the teams that end up announcing a delay instead.
The listing sells the app, so write it before you submit
Your title and subtitle carry most of the keyword weight the store algorithm sees. The first two screenshots decide whether anyone scrolls at all. The short description is read many times more often than the long one. Write every piece of it before submission, because on Apple a metadata change after the fact can trigger another review cycle.
Screenshots should sell an outcome rather than display a user interface. Caption each one, show the app mid-task instead of empty, and localise at minimum the languages where you already have users. Localised metadata reliably lifts conversion in markets you never deliberately targeted, and it costs an afternoon.
Choose the category deliberately. A crowded one buries you, while an adjacent one where your feature set is unusual can give you a chart position that compounds. Rating prompts matter too, but only after the user has completed the thing your app exists to do, never on first launch.
Instrument revenue and retention before the first install
Ship with analytics and revenue tracking already wired, because the questions you will ask in week one cannot be answered retroactively. You need activation, meaning the point at which a new user completes the core action, retention by cohort, and, if you charge, trial-to-paid conversion split by acquisition source.
Subscription billing is the piece teams most often build themselves and most often regret. Receipt validation, restores, grace periods, billing retry and cross-platform entitlement add up to weeks of work and a permanent maintenance tax. A dedicated billing layer costs less than the engineering time it removes.
Nearly all of this tooling has a free tier or a startup programme that covers the first year, which is precisely the period when you have no revenue to pay for it. The app development section of the directory lists the backend, analytics and subscription offers worth claiming before you submit, rather than after the credits would have helped.
Launch day, and the week that actually matters
Roll out in stages where the store lets you. Google supports a staged rollout on a new release, and Apple's phased release covers you from the first update onwards. A small early slice catches the crash that only fires on the oldest operating system you support. Watch your crash-free session rate hourly for the first day rather than daily, and keep a fixed build ready to push through expedited review.
Launch day traffic is not the signal anyone should optimise for. What matters is what that cohort does over the following days, because the shape of the curve determines whether paid acquisition will ever be viable. An app whose retention flattens can buy users profitably. One whose retention decays to nothing cannot, at any price.
The first update is where discipline usually breaks. You have feedback, a backlog and adrenaline, and the temptation is to ship all of it at once. Ship the crash fixes and the single onboarding change your data supports, keep the release cadence predictable, and treat the store listing as something you iterate on rather than something you finished.
The offers mentioned above
Pulled live from the directory, so what you see here is what the listing says.
RevenueCat
Developer Tools
Free under $2,500/mo revenue
Free planLink on plan
Firebase
Developer Tools
No-cost usage tier plus $300 credit if eligible
CreditsDirect link
Mixpanel
Data & Analytics
1 year free
Free periodLink on plan
Supabase
Developer Tools
$500 in credits for Antler companies
CreditsPartnerCode on plan
Also mentioned on this page with nothing currently on offer: Apple Developer Program, Google Play Console. We track them so you do not have to go looking.
App Development codes, all in one place
49 listings in App Development, with the redemption codes and programme links behind one subscription. Browsing is free.
Common questions
How long does app store review take?
Most reviews clear within a day or two, but first submissions and anything involving subscriptions or account deletion take longer. Plan for a week between submission and a confident launch date.
Can I launch on one platform first?
Yes, and it is usually the right call. Shipping on one store first halves your support surface and lets you fix onboarding before the second audience ever sees it.
What gets an app rejected most often?
Broken demo credentials, incomplete privacy declarations, and purchase flows for digital goods that bypass store billing. All three are avoidable before you ever hit submit.
Should I launch with a paywall?
Launch with the billing wired in even if the paywall is generous. Retrofitting subscriptions later means a second review cycle and a rebuilt onboarding flow.