iOS App Prelaunch Checklist: 21 Steps Before App Store Submission

TL;DR

A complete iOS app prelaunch checklist covers six phases: Apple Developer Program enrollment, build readiness and code signing, App Store Connect metadata, screenshots and app preview, TestFlight beta testing, and submission day. The 21 steps below are what indie devs actually do before hitting Submit in 2026. Skip any of them and you risk a rejection, a delayed launch, or a quiet first week. If you only have 30 minutes, focus on steps 8 through 15. The metadata fields and your App Store screenshots drive the first impression.

What real indie devs are saying

Indie iOS developers ask this question on Reddit roughly once a week. From r/iOSProgramming, one solo dev wrote: "I am trying to find if there is a checklist of something I should make sure I have done before submitting an app to the app store." On r/iOSAppsMarketing, another asked for "tips/advice/checklist for things I should make sure I do prior to launching my app on the App Store."

The most useful answer we found came from a developer on r/iOSProgramming who wrote: "After 9 Apple rejections across 5 apps, here's my pre-flight checklist." That phrase, pre-flight checklist, is the right framing. Treat your first submission like a pilot would treat an aircraft. Quick verification, every line, before you push the throttle.

This iOS app submission requirements list is built from those threads plus our own published-app history. Use it as a working iOS app release checklist or an app launch checklist for your team's project board.

Phase 1. Apple Developer Program

Step 1. Enroll in the Apple Developer Program

You need an active Apple Developer Program membership ($99 per year) to ship to the App Store. Enrollment usually approves in 24 to 48 hours for individuals. Companies often wait longer because Apple verifies a D-U-N-S number for the legal entity. Start this two weeks before your planned ship date. Renewal is automatic but will fail silently if your card on file expires, which is one of the slow ways your app vanishes from sale.

Step 2. Set up your Apple Developer account

After approval, complete your Apple Developer account profile. Add legal entity name, address, banking details, and tax forms in App Store Connect. Paid apps and apps with in-app purchases cannot accept money until Agreements, Tax, and Banking is fully green. Many first launches stall here, not in code review.

Step 3. Assign team roles in App Store Connect

Add your designer, your QA tester, and your marketing collaborator with the smallest role each one needs. Admin is rarely the right role for a contractor. The App Manager role can manage builds and metadata without seeing financials. Get this right before you upload a build, since some role permissions only apply to builds uploaded after the role was granted.

Phase 2. Build readiness and code signing

Step 4. Configure signing certificates and provisioning profiles

In Xcode, set Signing and Capabilities for the Release configuration to your team and your Apple Developer account. Use Automatic signing for indie projects. If you use Match or fastlane, regenerate certificates and profiles once per machine to avoid the classic "no profiles for bundle ID" error at archive time. This is the most common reason an otherwise ready build refuses to upload.

Step 5. Archive a release build, not a debug build

Run Product, then Archive in Xcode against a real device target, not a simulator. Confirm the archive shows up in Organizer with the right version and build number. Bump build number on every upload. Apple does not let you reuse a build number, even for a rejected submission.

Step 6. Static analysis, unit tests, and crash testing

Run your test suite one last time. Open Product then Analyze for the static analyzer. Open Instruments and run a 5 minute Time Profiler session on the main user flow. Look for runaway main-thread work, since first-launch lag is a common one-star review trigger. If you ship Firebase Crashlytics or Sentry, dogfood the production DSN on this build before you upload.

Step 7. Upload the build via Xcode or Transporter

Use Organizer to Distribute App, then App Store Connect, then Upload. Transporter.app is the fallback when Xcode hangs at "Processing." Apple takes 5 to 30 minutes to process a build after upload. The build appears under TestFlight inside App Store Connect once processing is finished, even if you have not configured TestFlight yet.

Phase 3. App Store Connect metadata

This is where most of your conversion math lives. Apple uses the App Store keywords field, your title, and your subtitle for indexing. Users see the title, subtitle, and first three screenshots.

Step 8. Name, subtitle, promotional text

Your title is 30 characters. Your subtitle is 30 characters. Pick a benefit, not a category. "Sleep tracker" loses to "Sleep coach in your pocket" in A/B tests, and your title is the first thing the App Store algorithm reads. Promotional text is 170 characters and is the only metadata field you can update without resubmitting for review. Use it for "now with widgets" type updates between releases.

Step 9. App Store keywords field

The app store keywords field allows 100 characters. Comma-separated, no spaces, no plurals (Apple stems them for you). Do not repeat words from your title or subtitle, since those already index. If you are not sure which 100 characters to spend, read our ASO keyword research guide for indie developers before you fill this field.

Step 10. Privacy nutrition label and ATT prompt

Open App Privacy in App Store Connect. Declare every data type your app or your SDKs collect. Crashlytics counts. Mixpanel counts. AdMob counts. If you show the App Tracking Transparency prompt, write the explanation string under Info.plist NSUserTrackingUsageDescription. The privacy nutrition label is one of the most common rejection causes for first launches.

Step 11. Age rating, content descriptors, export compliance

Answer the age rating questionnaire honestly. Most utility apps land on 4+. Export compliance for standard HTTPS apps is one checkbox stating you use only exempt cryptography. Apps that ship custom encryption need a yearly self-classification report.

Step 12. Support URL, marketing URL, and copyright

Support URL is mandatory and must resolve to a live page on submission day. A GitHub Pages stub with a contact email is fine for v1. Marketing URL is optional but boosts trust. Copyright line is the legal entity name, year first published.

Phase 4. Screenshots and app preview

Step 13. Master screenshots at 1290 by 2796 pixels

In 2026 you only need one master set per locale at 1290 by 2796 pixels. Apple auto-scales to every other iPhone. See our full App Store screenshot sizes 2026 guide for the iPad and Mac sister sizes. Upload at least 3 screenshots, since the first three are what the search-result card uses. Most Top 100 apps ship 6 to 8.

If you do not want to spend a weekend in Figma, ScreenFast generates 10 App Store screenshots from your App Store URL in under 2 minutes for $9.99 per app. Prelaunch developers can upload their own raw screenshots to ScreenFast and get the same 10 designs without needing a live listing.

Step 14. A/B test variant copy if you have prior data

Apple's Product Page Optimization lets you test 3 alternate creative sets against the default for 90 days. If this is your first launch, skip this step. After 30 days of live downloads, read our App Store screenshot A/B testing guide and start your first PPO experiment.

Step 15. Optional 30-second app preview video

App preview videos can lift install rate but cost a day of work. If you have time, ship a 15 to 30 second portrait clip at 1080 by 1920. Apple's spec is strict and rejection-prone for first-time submitters. Watch this 13 minute prelaunch walkthrough by Chris Raroque for an example workflow that includes the app preview step.

Phase 5. TestFlight beta testing

TestFlight beta testing catches the bugs that your local simulator never sees, and it warms up your first 50 to 500 users for launch day.

Step 16. Add internal testers (up to 100)

Internal testers are anyone on your App Store Connect team. They get builds immediately, no Beta App Review needed. Use this group for your core team and your trusted power-users. Internal builds also expire after 90 days.

Step 17. Invite external testers via public link

External testers can be up to 10,000 per app, by email or via a public TestFlight link. Their first build needs Beta App Review (24 to 48 hours, usually faster than App Store Review). Set up a Feedback Assistant URL so testers can ship screenshots and notes from inside the TestFlight app.

Step 18. Run a 7 day TestFlight cycle minimum

One day is not enough. Most crash reports surface on day 2 or day 3 when testers actually finish onboarding. Plan for at least a week of TestFlight before submission. If your beta returns no actionable feedback by day 3, your testers are inactive. Refresh the pool.

TestFlight option	Cap	Beta review	Use case
Internal testers	100	No	Team and power-users
External testers, email invite	10,000	Yes, first build	Friends, family, waitlist
External testers, public link	10,000	Yes, first build	Open beta, Reddit waitlists

Phase 6. Submission day

Step 19. Run a pre-submission rejection check

The four most common pre-flight catches are: privacy nutrition label gaps, Sign in with Apple missing when other social logins are present, in-app purchase products in Missing Metadata state, and a Demo Account that the reviewer cannot log into. Open every metadata page in App Store Connect, top to bottom, and tick each one. This 10 minute check has saved every launch we have shipped at least once.

Step 20. Pick your release strategy

In Version Release, choose one of three options. "Automatically release this version" ships the moment Apple approves you. "Manually release this version" gives you a green button to press, useful for coordinated launches. "Automatically release after App Review" with a scheduled date lets you target a launch window like a Tuesday at 09:00 in your primary market.

Step 21. Submit for App Review and monitor the queue

Click Add for Review, then Submit. Apple's median review time in 2026 is 24 hours, with a long tail. Watch the App Review status email and the App Store Connect dashboard. If you get an Information Needed note, reply inside the resolution center within 24 hours to keep momentum.

Common app store rejection reasons in 2026

App store rejection reasons cluster around metadata mistakes more than code mistakes. The list below comes from public review transcripts on r/iOSProgramming and our own rejections over 8 shipped apps.

Rejection guideline	Why it triggers	Fix
2.1 Information Needed	Reviewer cannot log in to test	Provide a demo account in App Review notes, confirm it works one last time
2.3.10 Accurate Metadata	Screenshots show features the app does not have	Match every screenshot caption to an actual screen in the app
4.0 Design Spam	App looks like an existing template	Add a unique value proposition to the title, subtitle, and first screenshot
5.1.1 Data Collection	Privacy nutrition label is incomplete	List every analytics, ad, and crash SDK you ship
5.1.4 Account Sign-In	Social login without Sign in with Apple	Add Sign in with Apple alongside Google or Facebook

How we tested

This iOS app prelaunch checklist comes from three data sources. First, we read the top 10 Serper organic results for "ios app prelaunch checklist" and "app store submission checklist" in late 2026 and pulled the steps that recurred across at least 3 of them. Second, we re-read our own internal submission notes from 8 shipped iOS apps, including 4 rejections we recovered from. Third, we mined live indie-developer threads on r/iOSProgramming and r/iOSAppsMarketing for pain phrases, then quoted only what appeared in the public Google SERP snippet. We do not cite upvote or comment counts from Reddit, since their public API blocks third-party scraping and any number we quoted would be a guess.

We disclose that ScreenFast is our own product. We used our screenshot pipeline for step 13 because we ship it. Where we recommend it, we link to our pricing page so you can see the $9.99 per app, pay-per-pack model. We have no affiliate links in this post.

Frequently asked questions

How long does App Store Review take in 2026?

Median App Store Review time is 24 hours, with most decisions returned in under 48 hours. Beta App Review for TestFlight external testers is usually faster, often under 24 hours. Holiday weeks (Thanksgiving, Christmas, Lunar New Year) push the tail closer to 5 days.

Do I need an LLC to publish on the App Store?

No. The Apple Developer Program enrolls individuals as well as organizations. Individuals publish under their legal name, which shows on the App Store listing. Many indie devs start as individuals, then move to an LLC after $1,000 of monthly revenue for tax and liability reasons. The migration requires a D-U-N-S number and Apple's transfer process.

What does the $99 Apple Developer Program get you?

Membership unlocks App Store distribution, TestFlight beta testing, all current developer betas of iOS, watchOS, tvOS, and visionOS, signing certificates for distribution and push notifications, and access to Xcode Cloud tier minutes. It is required for every paid or free app shipped to the App Store.

What is the most common App Store rejection reason for first apps?

Guideline 2.1 Information Needed, almost always for a missing or broken demo account in App Review notes. The reviewer cannot test gated features, so the reviewer rejects. The fix is a working test account with steps to reach every paid feature, written in the Notes field at submission.

How many beta testers can I add to TestFlight?

Up to 100 internal testers (anyone on your App Store Connect team) and up to 10,000 external testers per app. External testers can join by email invite or via a public TestFlight link. Internal testers do not need Beta App Review. External testers need Beta App Review on the first build only.

What size should my App Store screenshots be in 2026?

A single master set at 1290 by 2796 pixels for iPhone 6.9 inch displays. Apple auto-scales to every other iPhone form factor. iPad apps need a separate set. Read the full App Store screenshot sizes 2026 guide for the iPad and legacy sizes.

How do I deploy iOS app updates after launch?

Bump the version number in Xcode, archive a new release build, upload via Organizer or Transporter, fill in the What's New text in App Store Connect, and submit. Update-only metadata changes (promotional text) do not require a new build. This is the standard flow for how to deploy iOS app updates without resubmitting the binary.

Can I publish to the App Store for free?

You cannot. The Apple Developer Program costs $99 per year and is required for every App Store publication, paid or free.

Bottom line

A full iOS app prelaunch checklist is 21 steps in six phases. Most ship-day disasters trace back to phase 3 (metadata) or phase 5 (TestFlight), not to code. Get your Apple Developer account healthy in week one. Get your screenshots and app store screenshots metadata locked in week two. Run TestFlight beta testing for at least a week. Submit on a Monday, not a Friday, so you can respond to App Review notes inside business hours.

When you reach phase 4, save the design step. ScreenFast generates 10 App Store screenshots in 2 minutes for $9.99, or feeds raw uploads through the same pipeline for prelaunch projects. Then come back to step 14 once you have real install data, and read our App Store screenshot A/B testing guide to ship your first PPO experiment.

Last updated: 2026-05-19.