Mobile app launch. Full checklist.
Everything on the list before a mobile app launch: App Store review prep, Google Play requirements, ASO setup, launch-week comms, day-zero push strategy, and the post-launch first-month watch list.
Five phases, five weeks.
A mobile app launch in 2026 runs five phases across five weeks. Week minus four: complete App Store and Google Play metadata, privacy nutrition labels, and screenshots. Week minus three: TestFlight beta to a friends-and-family test pool; iron out crash reports and onboarding friction. Week minus two: submit to both stores; budget 24 to 48 hours for Apple review, 1 to 3 hours for Google Play, plus a 2-week buffer for rejection and resubmission. Week minus one: ready launch-week comms - email, SMS, in-site banner, organic social, paid campaigns on Meta and Apple Search Ads. Launch week: day-zero push strategy avoiding cold permission prompts, install-to-session metrics tracked hourly, 24/7 on-call for crash reports. Post-launch 30 days: track install count by channel, day-1 retention above 40 percent, day-7 above 20, day-30 above 10 - below those, iterate on onboarding and push before pouring more dollars into acquisition.
Metadata, screenshots, privacy.
App Store (iOS) metadata. Name (30 chars max), subtitle (30 chars), keywords field (100 chars, hidden from users but used by Apple Search), primary and secondary category, age rating. Privacy nutrition label: every data type the app collects, whether it is linked to the user's identity, whether it is used for tracking across apps. Apple's App Privacy Details documentation specifies the 14 categories and the requirement to enumerate every SDK that collects data.
Google Play metadata. App name (50 chars), short description (80 chars), full description. Content rating, pricing and distribution countries, target age group. Data Safety form, which is Google's equivalent of Apple's privacy label but slightly more permissive. Google's form asks about data collection, sharing with third parties, encryption in transit, and deletion-on-request support. Both stores require a valid privacy policy URL; many apps build a minimal policy on their main website pointing to a dedicated app-privacy page.
Screenshots. 6.7-inch iPhone (iPhone 15 Pro Max) at 1290x2796, 6.5-inch iPhone at 1242x2688 (still required for back-compat), iPad 12.9-inch, Android phone at 1080x1920 or 1080x2340, Android tablet. The first two screenshots do the conversion work; they show in the App Store preview before the user taps to see more. Lead with the most visually compelling and feature-differentiating screen. Standard practice: screenshot 1 shows the home / browse experience, screenshot 2 shows a differentiating feature (loyalty, customization, AR fit), screenshots 3 to 5 show secondary features.
TestFlight. Internal testing.
TestFlight (iOS) and Google Play Internal Testing are both-platform beta mechanisms. Upload the build, add 50 to 200 testers via email, they install the beta app and run it for 5 to 7 days of real use. The target: a broad enough test pool that edge-case devices (older iPhones, budget Android, various OS versions) all get coverage. Ideal mix: 40 percent employees and friends-and-family, 40 percent existing customer beta program, 20 percent recruited from user research.
What to watch during TestFlight. Crash reports in Firebase Crashlytics or Sentry - any crash rate above 1 percent is a blocker for launch. Onboarding drop-off - if 30 percent of testers never get past the first screen, the onboarding needs rework. Performance on older devices - a 2022 iPhone SE should handle the app smoothly; if it lags, the app needs optimization. Push notification delivery rates across iOS and Android - some builds have silent failures that only show up with a real device fleet.
The minimum 5-day TestFlight window catches 80 percent of issues. Running 10 to 14 days catches another 15 percent. Extending to 30 days catches the last 5 percent but delays launch. For brand launches tied to a marketing calendar, 10 days is typically the right tradeoff. Iteration during TestFlight should be daily builds with fix-verify cycles; slow iteration means issues compound and launch slips.
Submit. Handle rejection.
App Store submission flow. Upload binary to App Store Connect, attach it to a pending version, fill the review notes (especially for apps with behind-login functionality the reviewer needs credentials for), submit. Apple review typically returns 24 to 48 hours later with either approval, rejection with specific feedback, or request for more information. Reviewer-test-account credentials are the most overlooked field - omit them and the reviewer cannot test the app past the login screen, which is an instant rejection.
Google Play submission flow. Upload AAB (Android App Bundle, not APK) to Play Console, create a production track release, fill release notes, submit. Google's review is faster (1 to 3 hours typical) and more automated - most rejections come from the Data Safety form being incomplete or the APK having obvious issues like unsigned code. The feedback loop with Google is thinner than Apple's; you often just see a rejection reason without detailed guidance, which means Google submissions require more self-QA before submit.
Rejection response. Read the rejection carefully; Apple rejections cite specific App Store Review Guideline sections. Fix the issue, build a new binary, submit as a new version with detailed response notes in the review comments. Cycle time: 2 to 5 business days per rejection round. Plan 2 rejection rounds (4 to 10 business days total) into the timeline to be safe; a clean first submission without rejection is possible but not the average outcome.
Launch comms ready.
Five launch assets to have pre-approved and scheduled. Email to existing customers announcing the app with a universal link (a single URL that opens the App Store on iOS and Play Store on Android based on device). SMS announcement to opt-in subscribers via Postscript or Attentive. In-site banner or popup on the web store pointing to the app download, with device-detection logic to show iOS button to iOS users and Android button to Android users. Organic social posts across Instagram, TikTok, Twitter with a short demo video showing the app in use. Paid campaigns on Meta and Apple Search Ads targeting the brand name and category keywords.
Owned channels first. Email and SMS typically drive 40 to 60 percent of first-week installs for existing DTC brands. Paid channels follow after organic traffic validates the conversion funnel. Spend light on Meta in week one (10 to 20 percent of planned monthly budget) while testing which creative resonates; scale to full budget in weeks two and three once the install-to-purchase funnel has data.
The launch-week support plan. 24/7 on-call for crash reports, a shared channel for customer support team to escalate app-specific issues (differentiated from web issues), and a rapid-iteration build process that can ship a hotfix build to both stores within 4 hours of a critical issue being confirmed. Apple's expedited review process handles urgent bug fixes in 1 to 4 hours when requested with clear justification.
The metrics that matter.
Day 1: install count by channel, session 1 completion rate. If organic installs arrive without paid spend, the pre-launch comms worked. If session 1 completion is below 70 percent, onboarding is too long or confusing.
Day 7: day-1 retention (returning users on day 2), day-7 retention (active users on day 7). Healthy day-1 retention for commerce apps is 40 percent or higher; day-7 retention is 20 percent or higher. Below those thresholds, the first-run experience needs rework before scaling acquisition spend - paying for installs that never return is the fastest way to set ad-spend money on fire.
Day 30: day-30 retention, the north-star metric. Above 10 percent retention at day 30 means the app has found users who will use it long-term; the rest of growth is acquisition velocity. Below 10 percent means the app has product-market-fit problems that acquisition spend cannot solve. For related context, see the push notifications guide (which is usually the biggest retention lever) and the mobile app builders comparison if you are still deciding platform vs custom.
Six answers.
How long does App Store review actually take in 2026?
Apple App Store review averages 24 to 48 hours for standard submissions as of early 2026, down from the 7-day average of the 2019 era. Google Play review is faster, typically 1 to 3 hours for apps from established developers. First-time submissions from new developer accounts on either platform can take 7 to 14 days because the platforms run extra fraud and quality checks. The rejection rate on first submissions is around 20 to 30 percent, usually on items like missing privacy disclosures, broken sign-in flows, or metadata claims the app does not actually support. Plan a 2-week buffer between target launch date and submission to handle one rejection and resubmission cycle.
What gets an app rejected on first submission?
Six common reasons. One, incomplete privacy nutrition label on iOS or Data Safety form on Google Play; both platforms now require detailed disclosure of every data type collected. Two, broken sign-in flow during reviewer testing; Apple reviewers in particular walk the full sign-in journey and reject apps that cannot complete it. Three, guideline-violating content (claims the app does not support, imagery inconsistent with the app's actual function, clickbait screenshots). Four, in-app purchase using non-platform billing for digital goods (iOS specifically). Five, missing or unreachable support URL in the app listing. Six, misuse of private APIs that an automated scan flags. Most rejections resolve in 2 to 5 business days after a fix is resubmitted with clear notes to the reviewer.
How do I set up app store optimization (ASO) for launch?
Three layers. Layer one, metadata: app name (iOS: 30 chars max, Google: 50 chars), subtitle (iOS: 30 chars), short description (Google: 80 chars), long description. The primary keyword should appear in the app name and subtitle, not buried in the description. Layer two, screenshots: 3 to 5 screenshots both stores, the first two doing the work of convincing the user to tap install; lead with the feature a user would most want to use. Layer three, ratings and reviews: prompt for reviews after positive user actions (completed order, successful workout), not on cold app open. Initial ASO can be hand-tuned; for data-driven iteration, use AppTweak, Sensor Tower, or Data.ai for 100 to 500 dollars per month subscription.
What launch-day comms should be ready?
Five assets in the launch week package. One, email to the existing customer list announcing the app with a clear install CTA (universal link that opens App Store or Play Store based on device). Two, SMS campaign to opt-in SMS subscribers if the channel is live. Three, in-site banner or popup on the web store pointing to the app download. Four, organic social posts across Instagram, TikTok, Twitter with the app icon and a short demo video. Five, paid campaigns on Meta and Apple Search Ads targeting the brand name and category keywords. The mix emphasizes owned channels (email, SMS, organic social) first; paid channels follow once organic traffic confirms the app performs.
What should day-zero push notification strategy look like?
Three principles. One, do not ask for push permission at first launch; ask after a positive moment (completed first product view, added to cart). First-launch permission prompts get rejected by 60 to 75 percent of users on iOS; post-engagement prompts get accepted by 40 to 55 percent. Two, segment from day one; do not blast every user with every message. Segment at least by acquisition source (web-installed vs App Store-search vs paid ad) and by first-7-day engagement. Three, limit frequency to 2 to 4 messages per week in the first 30 days; above that users uninstall or disable push and the channel is dead. The goal in the first month is to earn the right to send, not to maximize sent volume.
What should I track in the first 30 days post-launch?
Eight metrics. Install count by channel (organic vs paid vs referral). Installs to first session (some installs never open the app). Session 1 completion rate (how many users get past first-load to a meaningful action). Day-1 retention (return on day following install). Day-7 retention (return within a week). Push-notification opt-in rate. Day-1 conversion rate (percent of installs that transact in 24 hours, relevant for commerce apps). Day-30 retention (the north-star metric for product-market fit on mobile). The pattern that distinguishes a working app from a struggling one: Day-1 retention above 40 percent, Day-7 retention above 20 percent, Day-30 retention above 10 percent. Below those numbers, iterate on onboarding and push before spending on acquisition.
Launch is operational craft.
Our mobile-app engagements cover end-to-end launch: App Store prep, TestFlight cycles, submission, rejection response, ASO setup, launch-week playbook, and the 30-day post-launch iteration sprint. Scoped quote in 48 hours.