How to submit your first app to the App Store

Shipping the build is the part most first-time app makers expect. The surprises come after: an agreement to accept, a privacy questionnaire, screenshots in exact sizes, a reviewer who cannot sign in, and a rejection message that points to a guideline number. None of it is hard once you know the order. This guide walks through that order for a first iPhone app.

It assumes the app already runs on your own device. If you are still deciding whether the idea deserves a build, start with the product validation guide.

Enroll and set up the accounts first

Publishing requires the Apple Developer Program, which Apple lists at $99 a year. Enroll as an individual if you publish under your own name, or as an organization if the app should appear under a company name. Organization enrollment needs a legal entity and extra verification, so start it early if that is your route.

• Accept the latest agreements in App Store Connect. Pending agreements quietly block uploads and paid features.
• Complete tax and banking details before release if the app or its in-app purchases are paid.
• Create the app record with a bundle ID that matches your Xcode project exactly.
• Choose the app name early. Names must be unique on the store, so check it before designing the icon around it.

Upload a build and test it with TestFlight

Archive the app in Xcode and upload it to App Store Connect. Once processing finishes, the build appears in TestFlight. Internal testers on your team can install it right away. External testers, up to 10,000 people by email or public link, need a beta description and a short beta review before they can install it.

Use TestFlight for a few days with real people on real devices. First launch, sign-up, the core task, and any purchase flow should all work without your help. A crash that only appears on an older iPhone is much cheaper to find here than in a one-star review.

Build a store page that explains the app in seconds

The store page is your landing page. The name, subtitle, and first screenshots carry most of the weight, because many people never scroll to the description. Apple accepts one to ten screenshots per display size, as JPEG or PNG without transparency. Check the current screenshot specifications in App Store Connect help before exporting, since the required device sizes change as new iPhones ship.

1. 1Lead with the outcome in the first screenshot, not the settings screen.
2. 2Give each screenshot one short caption that names a benefit.
3. 3Show the real interface. Mockups that do not match the app invite rejection and disappointed users.
4. 4Write keywords as a comma-separated list without repeating words already in the name.

Answer the privacy questions honestly

Every new app and update needs privacy details in App Store Connect: what data the app collects, whether it is linked to the user, and whether it is used for tracking. Include what third-party SDKs collect, such as analytics or crash reporting. You also need a public privacy policy URL, and Apple requires a working support link with current contact information.

If your app lets people create an account, it must also let them delete that account from inside the app. This requirement catches many first submissions. Build the deletion path before review rather than after a rejection.

Ship Your First App Kit: a guided path through the first submission

Ship Your First App Kit walks first-time app creators through nine stages, from getting ready and uploading a build to App Review, going live, and publishing the first update. It pairs a web companion with task checkboxes and saved notes, four printable PDFs, and fifteen App Store screenshot templates.

It is a one-time purchase and includes an optional support branch for handling a rejection. It suits a solo maker who wants a checklist to keep their place across several evenings. Still check each step against Apple’s current guidelines, because the requirements change over time.

Prepare the reviewer, then submit

Apple states that on average 90% of submissions are reviewed in less than 24 hours. A clean first review depends mostly on giving the reviewer everything they need in the App Review Information section.

• Provide an active demo account or a fully featured demo mode if any feature needs sign-in.
• Explain anything that is hard to reach: hardware, a location, a QR code, or a special configuration.
• Remove placeholder text, test content, and broken links. Incomplete apps are a common rejection reason.
• Make sure the app does more than wrap a website. Apple expects lasting utility beyond a repackaged web page.

Choose manual release if you want to control the launch moment. The app then waits after approval until you press release, which lets you line up your announcement, launch listings, and support inbox first.

Handle a rejection without panic

A rejection is a message, not a verdict. Read the guideline it cites, fix the specific issue, and reply in Resolution Center with what changed. If you believe the reviewer misunderstood the app, explain calmly with steps and screenshots. Keep every reply factual and short.

Plan the first update before launch day

Your first real users will find bugs and confusion you did not. Keep a short list of fixes you already know about, and plan an update for the first week or two. Updates go through review too, so a small, focused release gets back to users faster than a large one.