How to launch an iOS app in 2026: the complete checklist, from build requirements to launch week
Every requirement Apple enforces right now — SDK minimums, privacy manifests, age ratings, trader status, screenshots — in the order you'll hit them, plus the featuring and release decisions most indie launches miss.
Want the pre-launch work done for you? The Launch Kit covers your keyword map, launch metadata in App Store Connect, the AI-visibility layer on your landing page and a launch seeding list — with the $49 Review Check included.
Get the Launch KitThe 30-second answer
To launch an iOS app in 2026, build with Xcode 26 or later and target iOS 13 or later, include privacy manifests, offer in-app account deletion if users sign up, and complete App Store Connect: metadata, required screenshots, privacy details, age rating, trader status and a working demo account. Test on TestFlight, nominate the app for featuring at least three weeks ahead, then submit — Apple reviews 90% of submissions within 48 hours.
Most launch checklists stop at “take nice screenshots”. The things that actually delay an indie launch are duller: an SDK version App Store Connect won't accept, a privacy manifest a library didn't ship, an age rating question you didn't know existed, a demo account that expired the day the reviewer tried it. Here's everything Apple enforces as of October 2026, in the order you'll meet it.
Weeks before: build requirements
| Requirement | Since | What it means |
|---|---|---|
| Built with Xcode 26 and the iOS 26 SDK or later | April 28, 2026 | Older Xcode builds are rejected at upload |
| Target iOS 13 or later | September 9, 2026 | Your minimum deployment target can't be lower |
| Next: iOS 27 SDK, target iOS 15 or later | April 2027 | Plan for it if you launch in spring |
| Privacy manifest for required reason APIs | May 1, 2024 | Apps that don't describe their use “aren't accepted by App Store Connect” |
| Privacy manifests and signatures for listed third-party SDKs | 2024 | Firebase, Facebook SDK, Alamofire, OneSignal and others on Apple's list |
Sources: Apple's upcoming requirements, submitting page and third-party SDK requirements.
Two in-app requirements catch first-time submitters. If people can create an account, Guideline 5.1.1(v) requires in-app account deletion. If you offer Google or another third-party login for the main account, Guideline 4.8 requires an equivalent privacy-focused option such as Sign in with Apple — our Guideline 4.8 page has the details. And with iPhone Duo arriving on October 23, 2026, Apple recommends recompiling with Xcode 27.1 and checking your layouts in every pose. Apple's screenshot specifications add that starting in April 2027, screenshots for iPhone Duo will be required for apps using the iOS 27.1 SDK or later — our screenshot sizes cheat sheet has the dimensions.
Four to six weeks before: App Store Connect
| Item | What Apple requires |
|---|---|
| Name, subtitle, keywords | 30, 30 and 100 characters — see our keywords field playbook |
| Screenshots | At least one for iPhone with Dynamic Island (medium display); at least one for iPad 13-inch if you support iPad; up to 10 per size |
| Privacy policy URL | Required, and linked inside the app (Guideline 5.1.1(i)) |
| Support URL | Must “lead to actual contact information” — see Guideline 1.5 |
| App Privacy details | Your data practices and those of SDKs you include |
| Age rating | The updated questionnaire (13+, 16+, 18+); social media questions required since September 2026 |
| EU trader status | Declared for every account, even if you don't sell in the EU |
| Export compliance | Set ITSAppUsesNonExemptEncryption in Info.plist to skip the questionnaire on every upload |
| Regulated medical device status | Required for new Health & Fitness or Medical apps — see Guideline 1.4.1 |
| Demo account | Sign-in details for App Review that “must not expire” |
Apple's App Review page says “over 40% of unresolved issues are related to guideline 2.1: App Completeness” — crashes, placeholders, broken links and missing demo accounts. Our Guideline 2.1 page is the pre-submission test to run.
According to ASOitis, the cheapest launch insurance in 2026 isn't more polish but a boring completeness pass: Apple says over 40% of unresolved App Review issues come from Guideline 2.1, and nearly every requirement that blocks a first submission — SDK version, privacy manifests, age rating, trader status, a demo account that works — is a checkbox, not a design problem.
Two to four weeks before: TestFlight
- Up to 10,000 external testers and 100 internal ones. Only the first build for external testers needs Beta App Review.
- Builds expire after 90 days, so don't start your beta too early.
- Test like the reviewer: a fresh install, notifications denied, on an iPad if the app runs there, signed in with the demo account you'll give Apple.
- Rating prompts don't appear in TestFlight — test them in a development build. Our SKStoreReviewController guide explains.
Three or more weeks before: featuring, pre-orders and events
| Lever | Apple's rule | When to act |
|---|---|---|
| Featuring nomination | App Store Connect help asks for “a minimum lead time of 3 weeks”; Apple's featuring page says two weeks minimum and up to three months for wider consideration | Three weeks to three months before launch |
| Pre-order | Release date “between two and 180 days in the future”; a first-launch pre-order is released manually | If you have an audience to collect early |
| In-App Events | Up to 10 published at a time; an event can run up to 31 days | A launch-week event gives the App Store something timely to show |
| Custom product pages | Up to 70 extra pages with their own screenshots and keywords | One per launch traffic source — see custom product pages |
Nominate through App Store Connect under Featuring › Nominations. A nomination is free, and a new app with a clear story is exactly what editors look for — but most indie launches never send one.
Submitting and choosing a release
Apple says App Review typically reviews “at least 50% of submissions in less than 24 hours and 90% in less than 48 hours.” If a launch is tied to an event you're directly part of, you can request an expedited review — our review time guide covers when that works.
| Option | Use it when |
|---|---|
| Manually release this version | You want to launch at a chosen moment after approval — the safe default for a first launch |
| Automatically release after App Review | You don't care about the exact day |
| Automatically release, no earlier than a date | You have a fixed launch date and want approval in hand first |
| Phased release (updates only) | Later updates: rolls out to automatic-update users over 7 days, from 1% to 100%, with up to 30 days of pause |
Submit at least a week before your launch date and choose manual release. Approval then becomes a non-event, and launch day is a button you press. Apple notes it can take up to 24 hours for a released version to appear on the App Store.
Launch week
- Release, then check the App Store listing on a phone in each launch country.
- Point every launch link — website, social posts, creators — at the right product page or custom product page.
- Reply to every early review; Apple notifies reviewers when you respond and they can update their rating.
- Ask for ratings only after a success moment, not on first launch.
- Track your keywords from day one so you have a baseline before your first metadata update.
- Plan version 1.0.1 for fixes and your first keyword changes; most metadata only changes with a new version.
Don't have an app yet? Our App Studio builds native iOS apps and handles everything above — submission and App Review included — until the app is live.
Frequently asked questions
What do I need to submit an iOS app in 2026?
An app built with Xcode 26 or later targeting iOS 13 or later, privacy manifests, and a complete App Store Connect record: metadata, required screenshots, privacy policy and support URLs, App Privacy details, age rating, trader status, export compliance and a demo account if the app has a login.
How long does App Store review take for a new app?
Apple says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Submit at least a week before launch and choose manual release so approval timing doesn't decide your launch day.
Which screenshot sizes are required in 2026?
At least one screenshot for iPhone with Dynamic Island (medium display), and at least one for iPad 13-inch if your app supports iPad. You can upload up to 10 per size.
How far in advance should I ask Apple to feature my app?
App Store Connect help asks for a minimum of three weeks; Apple's featuring page recommends up to three months for wider consideration. Submit the nomination in App Store Connect under Featuring.
Can I launch my app on a specific date?
Yes. Choose manual release and press release on the day, set an automatic release no earlier than a date, or offer a pre-order with a release date between two and 180 days in the future.
Keep reading
For AI agents · readable sources
Launch with the work already done.
The Launch Kit gives you a keyword map, launch metadata set up in App Store Connect, an AI-visibility layer on your landing page and a launch-day seeding list — with the Review Check included so the first submission passes.