How to Submit an App to the App Store: The 2026 Walkthrough

Submission is not one action. It is roughly forty small ones, and any of them can hold up a launch by a week. Here is the order that avoids most of the waiting.

1. Apple Developer Program membership

$99 a year. Enrol as an individual and your legal name appears as the seller; enrol as a company and you need a D-U-N-S number for the entity, which can take a fortnight to obtain if you do not already have one. Start here, not last.

2. App Store Connect record

Create the app with its bundle ID, primary language and category. The name must be unique across the store and can be up to 30 characters; the subtitle another 30. Both are indexed for search, so use them.

3. In-app purchases, before the build

If you sell anything digital, create the products first and attach them to the build. Each needs a display name, a review screenshot and pricing across territories. Submitting a build whose purchases are not ready is the most common cause of a wasted review cycle.

4. Privacy labels and policy

Declare every category of data the app collects, including anything your analytics or crash reporting picks up. The answers must match your privacy policy, which needs a live public URL. Mismatches are rejected under guideline 5.1.

5. Screenshots and icon

At minimum you need the current 6.9" iPhone set; add iPad if you support it. Ship the icon as a square with no transparency and no pre-applied rounded corners. Screenshots are marketing, not documentation — the first two are what people see in search results.

6. Build upload and TestFlight

Upload with Xcode or Transporter, wait for processing, then run the build on a real device through TestFlight. Check cold start, sign-in, purchase, restore, push, and what happens with no network. Reviewers test exactly these.

7. Reviewer notes and demo account

Give working credentials for an account with content in it, plus a short note explaining anything unusual. A reviewer who cannot get past your login rejects within hours, and you lose a day.

8. Submit

Before you press send, run the launch checklist and confirm your screenshots match the build. Answer export compliance and content rights, choose manual or automatic release, and send it. Review is typically 24 to 48 hours, longer in the weeks before major holidays. Expedited review exists for genuine emergencies and should be saved for one.

If you are rejected

Read the guideline number, fix precisely that, and reply in Resolution Center rather than uploading a new build if no code change is needed. A clear, polite reply frequently resolves the issue without another cycle.

If you would rather not learn all of this on your first launch, we do it as a managed service — on your developer account, so you own the app at the end.