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
- 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).
- 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.
- 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.
- 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).
- 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.
- 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.
- 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:
- Add the app to get its slug and API key.
- 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.
- Call
configureat launch, passing your RevenueCat user id when you use RevenueCat so revenue events join the app events. It sendsfirst_openonce per install,app_openeach session and the Apple Search Ads attribution token automatically. - Add the fixed events: one call per onboarding screen, in order, then the paywall events.
- 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.