Guide · 8 min read
Indie App Launch Checklist: The 6-Week Plan for 2026
Two policy changes in early 2026 rewrote the indie app launch timeline. Apple now rejects any submission not built with the iOS 26 SDK — a mandate that took effect April 28, 2026. Google Play now requires new personal developer accounts to complete a 14-day closed testing period with at least 12 testers before gaining access to production. Both changes add mandatory lead time that most launch guides written before 2026 don't account for. This is the 6-week timeline that maps around both gates, with the right work in the right order.
Week 6: Apple's iOS 26 SDK mandate is your non-negotiable starting gate
Starting April 28, 2026, Apple rejects any app or update submitted to the App Store that was not built with the iOS 26 SDK or later. This applies to new apps and to updates of apps already on the store. You cannot ship without it. The practical consequence: your first task at week 6 is confirming you are building in Xcode 26 and that your project compiles cleanly against the iOS 26 SDK. This takes an afternoon for most apps; it can take a week for projects with heavy third-party SDK dependencies that haven't shipped their own iOS 26-compatible releases.
Critically, the SDK requirement does not force you to raise your deployment target. You can build with the iOS 26 SDK and still support devices running iOS 16 or iOS 17 by setting a lower deployment target in your project settings. The two settings are independent. What the SDK requirement does enforce is that your binary includes the APIs and privacy manifest declarations introduced in iOS 26 — specifically, every third-party SDK you include must ship a valid PrivacyInfo.xcprivacy file, or your submission will trigger a privacy manifest warning that can delay or block review.
Run your privacy manifest audit at week 6, before you invest time in screenshots and store copy. Check every Pod, Swift Package, or manually-embedded framework against Apple's upcoming requirements list. Any SDK missing a manifest needs an updated version — and if no update exists, it may need to be replaced. Discovering this at week 1 collapses your timeline; discovering it at week 6 leaves room to fix it.
Week 5: Google Play's 14-day closed test — the gate that catches Android-first launchers
If you are launching on Android from a personal Google Play developer account, you cannot go directly to production. Google now requires a 14-day closed testing period with a minimum of 12 distinct testers who have each opted in and installed the app. All 12 must complete the opt-in before the clock starts. Google's review team checks this before granting production access — it is an explicit gate, not an informal recommendation. A launch timeline that doesn't start the closed test at week 5 will collide with this gate at the worst possible moment.
The mechanics: in Google Play Console, create a closed test track, upload your APK or AAB, and send the opt-in link to testers. Testers must be signed into the Google account they share with you, accept the invite, and install the build. The 14 days start when Google confirms you've met the 12-tester threshold. Testers don't have to actively use the app during the period — they just have to have installed it. Use developer friends, beta subscribers, or communities like r/betatesting to hit the number quickly. Waiting until week 2 to start this process means your Android launch will be two weeks later than your iOS launch at best.
Week 4: Screenshots and icon first — because they have the longest iteration cycle
Screenshots are the asset most indie developers design last and the one that takes the most revision rounds to get right. The gap between a first attempt and a polished final set capable of converting cold traffic is typically three to five design iterations. At week 4 you have enough time for those rounds; at week 1 you don't. The instinct to defer screenshots until 'everything else is done' is the single most common reason indie apps ship with placeholder-quality store visuals that undercut everything else in the listing.
Start with your first screenshot — the one that appears in App Store search results before users tap to expand. This is the frame that determines whether a user taps through. It should show an outcome, not a home screen. A fitness app shows a completed workout. A habit tracker shows a streak. A budget app shows a net-positive month. The screenshot formula guide covers the seven patterns that consistently convert; the AppsTemple editor lets you build each one at the exact pixel dimensions Apple and Google require, then iterate without re-exporting from scratch each round.
Start your app icon at the same time. The icon displays in App Store search results before screenshots load, and it's the only visual asset that appears on the device home screen, in Spotlight, and in the App Store simultaneously. A weak icon taxes every other asset in your listing. With iOS 26 Liquid Glass rendering, icons now appear in standard, dark, and clear (transparent) modes — submit explicit dark and tinted variants in your Xcode asset catalog rather than relying on Apple's automatic inversion, which frequently looks wrong.
Week 3: Lock ASO metadata before screenshots are final — not after
Since June 2025, Apple uses OCR to index the text that appears as captions on your screenshots. This means your keyword set and your screenshot copy are the same decision, not separate ones. The correct order is to finalize your title, subtitle, and keyword field at week 3 — while screenshots are still in design — so the caption text on each frame can target the keywords you've already committed to. Locking metadata after screenshots are done usually means reworking captions you just finished, or shipping screenshots with caption text that misses your target keywords entirely.
Your 160-character keyword surface is: 30 characters in the app title (highest weight), 30 in the subtitle (second highest), and 100 in the keyword field (comma-separated, no spaces after commas, no repetition of title or subtitle terms). These three fields, combined with screenshot caption text, are the entirety of what Apple indexes for keyword matching on iOS. The long description is not indexed. Fill the keyword field with terms that don't already appear in your title or subtitle — repeating keywords wastes characters without adding ranking weight. The ASO keyword research guide covers how to build an efficient 100-character set without paid tools.
Week 2: Submit to TestFlight and budget for first-submission review time
Apple's stated review time for app submissions is 24–48 hours. That applies to routine updates of established apps. First-time submissions average 3–5 business days, and submissions that trigger a manual review — common for apps that include payments, user-generated content, or location access — can run 5–7 days. Submitting at week 2 rather than days before launch gives you exactly one chance to receive a rejection, fix the issue, and resubmit without pushing your launch date. Submitting at week 1 gives you no buffer at all.
The most common first-submission rejection reasons that delay timeline: screenshots that don't match the actual app UI, missing privacy policy URL (required for any app requesting user data), IAP products not set up in App Store Connect before submission, or app metadata that uses Apple trademark terms improperly. All of these are fixable in hours — but only if you have hours available. A TestFlight build submitted at week 2 also gives you a final round of real-device QA under App Store distribution conditions, which catches issues that Simulator testing misses. Monitor your crash rate in TestFlight; Apple's internal quality threshold for algorithmic featuring is reportedly near 99% crash-free sessions.
Launch day: Tuesday or Wednesday, synchronized channel hits, no Friday launches
Friday launches are a persistent bad habit among indie developers. The reasoning is usually 'people have more time to download apps on weekends,' which is true — but it ignores what happens when your app has a Day 1 crash spike at 6 PM Friday. You have 60+ hours before any meaningful Apple support response is possible, no developer community actively watching Reddit or X, and no way to expedite an emergency update review over the weekend. Tuesday and Wednesday launches give you the full work week to watch crash rates, respond to early reviews, and push a fix build if needed.
On launch day, coordinate your community channel hits simultaneously rather than sequentially. A post on r/SideProject at 9 AM and a Product Hunt launch at the same time and a newsletter send in the same window creates a cross-platform attention spike that each channel amplifies. Staggering them over a week dilutes the effect — each audience sees a quieter signal and fewer cross-channel reinforcements. If you're doing Product Hunt, aim for 12:01 AM PST on your target day to maximize your window in that day's ranking cycle. One synchronized push outperforms three scattered ones.
Post-launch week 1: the retention signals that determine whether you rank or stall
App Store ranking now weights post-install behavior signals — Day 1 retention, session frequency, redownload rate — heavily enough that a bad first week measurably suppresses organic keyword ranking going forward. Apple interprets rapid uninstalls as a quality signal. An install spike from a poorly targeted campaign, followed by high uninstall rates, can lower your ranking position even as it increases your download count. The practical implication: your post-launch priority is making sure users who install actually open the app more than once, not just maximizing raw install volume.
Watch your crash-free session rate in App Store Connect before you do anything else on launch day. A rate below 99% in the first 48 hours is worth an emergency fix build — not because users complain loudly, but because crash rate is the one signal Apple acts on fastest. Users don't leave reviews about crashes; they just delete the app, which is the worst outcome for your retention-rank signal. Day 3 is the right time to trigger your first in-app review prompt for users who've completed your core flow — not Day 1. Prompting too early yields lower star averages from users who haven't yet formed an opinion. The onboarding retention guide covers the flow design that maximizes that Day-3 return rate.
Build your store listing while the timeline still gives you room to iterate
The 6-week runway exists because compressing it creates specific, predictable failures — not because launches need six weeks of work. Apple's SDK compliance audit, Google Play's closed test, and multiple rounds of screenshot iteration each have hard time requirements that can't be parallelized past a certain point.
The assets that benefit most from starting early are screenshots and the app icon: they have the longest iteration cycle and the highest conversion impact. AppsTemple's editor lets you build and iterate on both at exact App Store and Play Store dimensions, with device frames, without a design tool subscription.
Build your launch screenshots in the editor →
Frequently asked questions
how long does it take apple to review an app for the first time?
First-time app submissions to the App Store average 3–5 business days for review, not the 24–48 hours quoted for routine updates. Apps that include in-app purchases, user-generated content, location access, or health data may trigger a manual review that extends this to 5–7 days. Budget at least 2 weeks before your target launch date for submission — one round for the first submission, one buffer round in case of rejection and resubmission.
does google play require a closed testing period before launch?
Yes, for new personal Google Play developer accounts created after 2023. You must complete a 14-day closed testing period with a minimum of 12 distinct testers who have opted in and installed the app. The 14-day clock starts after Google confirms you've met the 12-tester threshold. Without completing this period, Google Play Console will not grant access to the production track. Enterprise accounts set up through an organization are not subject to this requirement.
what is the minimum ios version i need to target for app store submission in 2026?
There is no minimum deployment target imposed by Apple — you can still support iOS 16 or lower by setting a lower deployment target in your Xcode project. The requirement that changed in April 2026 is the build SDK: all submissions must be built with the iOS 26 SDK or later (Xcode 26 or later). Building with iOS 26 SDK while targeting iOS 16 is fully supported — the two settings are independent.
when should i ask for app store reviews after launch?
The highest-quality timing for a first review prompt is Day 3 post-install, triggered after the user has completed a meaningful interaction with your core feature — not on first launch, and not on a timed delay. Day-1 prompts yield lower star averages because users haven't formed an opinion yet. Users who have completed your core flow at least once, and return on Day 3, are exactly the cohort with the strongest positive signal. Use Apple's SKStoreReviewRequest API, which respects Apple's system-level frequency cap (maximum three prompts per 365 days).
what day should i launch my app?
Tuesday or Wednesday. Friday launches are the most common mistake in indie app launch timing: if your app has a Day 1 crash spike, you have 60+ hours before the full work week resumes and emergency review requests can be escalated. Tuesday and Wednesday give you the full work week to monitor crash rates, respond to early reviews, and submit a fix build if needed before the weekend. Avoid Monday as well — review queues from the weekend can add extra variance to update turnaround times.