ActivationPal

How to Launch an App: Pre-Launch Checklist

To launch an app, finish the store listing, keywords and pricing before you submit, add analytics before the first public build, and check installs, onboarding, paywall and purchases daily for the first week. This checklist follows that order.

App launch checklist before you submit

  1. Validate the idea with the people you want. TalkingParents surveyed the customers of its web app before building the mobile app, and Wavve Boating showed a prototype map on iPads at a boat show before an app existed. CardPointers shipped a progressive web app first and reached 5,000 users on it before building the iOS app (RevenueCat).
  2. Finish the store listing. On the App Store product page, the name and the subtitle are up to 30 characters each. You can add up to 10 screenshots, and the first one to three appear in search results. You can also add up to three app previews of up to 30 seconds. The first sentence of the description is the one people read without tapping "more". Promotional text is up to 170 characters and can change without a new version. Pick the primary category carefully: it decides where the app shows when people browse.
  3. Choose the keywords. The keyword field holds 100 characters, comma-separated with no spaces. Leave out plurals of words already included, category names, the word "app" and duplicates. How to find keywords for the App Store covers where to get candidates, the keyword checker scores a term, and the ASO tools directory lists the options.
  4. Complete the required forms. Answer the age rating questionnaire and enter the privacy details in App Store Connect. Apple requires the privacy details to submit a new app (submitting to the App Store).
  5. Set pricing. Decide between free, free trial and paid, and pick the plan lengths. Prices can differ by country: see localized pricing for apps and the country pricing tiers. Enrolling in the Apple Small Business Program lowers the commission.
  6. Test a TestFlight build end to end, purchase flow included. TestFlight takes up to 100 internal testers from your team and up to 10,000 external testers by email or public link. Your first build for external testers goes through App Review. Testers send screenshot feedback, and you get crash reports.
  7. Start a waiting list. RevenueCat names it the way to build anticipation and acquire users before the app is available. Nomorobo used the media attention from winning the FTC Robocall Challenge to publicize the app.

Add analytics before release

Install the analytics before the build you submit, so the first user is already counted. With ActivationPal the setup is five steps, all in the quickstart:

  1. Add the app to get its slug and API key.
  2. Add the SDK. The native Swift SDK is one file with no dependencies and needs iOS 15 or later. Android, Flutter and React Native / Expo are supported too.
  3. Call configure at launch, passing your RevenueCat user id when you use RevenueCat so revenue events join the app events. It sends first_open once per install, app_open each session and the Apple Search Ads attribution token automatically.
  4. Add the fixed events: one call per onboarding screen, in order, then the paywall events.
  5. Connect the RevenueCat webhook (or Superwall's) in the setup checklist and paste its signing secret, so purchases, trials and refunds join the app events.
ActivationPal.configure(app: "myapp", key: "ap_pk_YOUR_KEY", userId: Purchases.shared.appUserID)

ActivationPal.onboardingStep(0, id: "goal", answer: "lose_weight")
ActivationPal.onboardingStep(1, id: "notifications")
ActivationPal.onboardingCompleted()

ActivationPal.paywallShown("onboarding")
ActivationPal.paywallPlanSelected("yearly")
ActivationPal.paywallPurchased("yearly")

Then run a TestFlight build. Events reach the live feed seconds later, and the env field separates debug, testflight and release, so test sessions stay apart from real ones.

Launch day

  1. In App Store Connect, select the build you tested in TestFlight and submit it for review. Submit early: review time is Apple's.
  2. Release the approved version.
  3. Message the waiting list and post in your own channels.
  4. Open the live feed and confirm first_open events arrive with env set to release.

How to get your first users

  • The waiting list and your audience. Everyone from the pre-launch steps gets the link first.
  • App Store search. Keywords, name and subtitle decide which searches show the app. Revisit them after the first week (keyword guide).
  • Custom product pages. Apple lets you create extra product pages with their own screenshots, app previews and promotional text. Each has its own URL, so you can send each audience to the page that fits it, in marketing or in an Apple Ads campaign.
  • Apple Ads on iOS. The Apple Ads card shows spend, ads-attributed revenue, installs and CPI by campaign, next to your organic installs (Apple Search Ads attribution). The setup is in the docs.

First-week metrics to watch

Read these once a day. Each one answers a different question about where users stop.

MetricWhat it measuresWhere to read it
InstallsDevices that opened the app for the first timeInstalls card
Onboarding completionShare of installs that finished onboardingOnboarded card and the onboarding funnel, step by step
Paywall conversionShare of users who saw the paywall and purchasedPaywall card: shown, plan selected, purchased
Trial outcomesTrials started, converted, pending or churnedOutcomes card
Revenue and ARPURevenue, and revenue per userRevenue and ARPU cards
Apple Ads CPI vs organicCost per ad-attributed install next to installs from other sourcesApple Ads card and the source column in Acquisition

Onboarding completion is completed divided by installed: 1,000 installs and 700 completed onboarding is 70%. Look first at the onboarding step with the largest drop, because every later metric inherits that loss.

Judge trials only after the trial length has passed. A 7-day trial that started yesterday has not had the chance to convert. App conversion rate and trial conversion rate show how each number is counted. ActivationPal puts all of these on one dashboard per app.

Frequently asked questions

How long before launch should I start?

Start the waiting list and the analytics setup before you submit, because the SDK ships inside the build you send to review. Test the purchase flow in TestFlight before that submission. How long App Review takes is Apple's call, so leave room between submitting and the date you announce.

How do I launch an app with no audience?

Show a prototype to the people you want as users, as Wavve Boating did, and survey them on what they would pay for. A public TestFlight link needs no contact list: you can set device type and OS version criteria for who joins, and disable the link when you hit your tester limit. Keyword work is how people who have never heard of you find the app.

What should I do in the first hour after release?

Send the link to your waiting list first, then watch the live feed. Once the first real installs arrive, walk through onboarding yourself on the release build and confirm the onboarding and paywall events show up in order. Every user who passes a missing step before you fix it stays a gap in your funnel.

Should I run Apple Ads at launch?

Start with one small campaign and wait until the first purchases arrive. Compare each campaign's CPI and ads-attributed revenue, and add budget only where the revenue covers the spend. User acquisition cost shows how to calculate CPI and payback.