How to Publish an iOS App on the App Store: Complete Walkthrough

Releasing an iPhone app involves several Apple-specific steps: a paid developer membership, signed builds, a listing in App Store Connect, privacy disclosures and an App Review. None of it is difficult, but the order matters and small mistakes cause delays. This walkthrough takes you through the process.

Apple updates its tools and rules regularly, so confirm the current details in Apple’s developer documentation as you go.

Step 1: Join the Apple Developer Program

• Enrol with an Apple ID using two-factor authentication
• Pay the annual membership fee (check the current amount, and note that fee waivers exist for some eligible organisations)
• Choose individual or organisation enrolment. Organisations usually need a legal entity and a D-U-N-S number, and verification can take time.

The name on your account becomes the seller name shown on the App Store, so choose the right type from the start.

Step 2: Prepare your app and identifiers

• You need a Mac with Xcode, Apple’s development environment. Cross-platform frameworks still use Xcode to build the iOS version.
• Register a unique bundle identifier for your app
• Set up capabilities you need, such as push notifications or in-app purchases
• Use automatic signing in Xcode where possible, which manages certificates and provisioning profiles for you

Before you build, remove debug code and test credentials, and review the mobile app security checklist.

Step 3: Meet design and content requirements

Apple reviews apps against its App Review Guidelines. Read them before you submit. Frequent trouble areas include:

• Apps that are too simple or are essentially a website wrapper
• Broken links, crashes and placeholder content
• Incomplete features or missing demo accounts
• Misleading descriptions or screenshots
• User-generated content without reporting and blocking tools. See trust and safety for social apps.
• Using external payments for digital goods where Apple requires in-app purchase (rules vary by region and change over time)

Also follow the Human Interface Guidelines so the app feels at home on iOS.

Step 4: Create the app in App Store Connect

In App Store Connect, add a new app with a name, primary language, bundle ID and SKU (your own internal identifier). Then complete the app information:

• Name and subtitle
• Category
• Description and keywords
• Support URL and, ideally, a marketing URL
• Privacy policy URL
• Age rating questionnaire

Review the ASO guide and keyword research guide to write these fields well. Remember that Apple indexes the title, subtitle and keyword field for search.

Step 5: Add screenshots and previews

Upload screenshots for the required device sizes, and optionally an app preview video. Follow Apple’s current specifications. Our article on screenshots that convert explains how to design them.

Step 6: Complete App Privacy details

Apple requires you to describe what data your app and its third-party SDKs collect, how it is used and whether it is linked to the user or used for tracking. These appear as “privacy nutrition labels” on your page. Be accurate: mismatches between your declaration and actual behaviour can lead to rejection. If you track users across other companies’ apps and websites, you must also use the App Tracking Transparency prompt.

Step 7: Upload your build

Archive the app in Xcode and upload it to App Store Connect (or use command-line tooling or your CI service). Once processed, the build becomes available to select for TestFlight and for release.

Step 8: Test with TestFlight

TestFlight is Apple’s beta testing platform.

• Internal testers (your team) can test quickly
• External testers can be invited by email or public link, and the first external build typically goes through a lighter beta review

Gather feedback and crash reports, fix issues and upload new builds as needed.

Step 9: Submit for review

Select the build, add release notes (“What’s New”), provide review notes and demo credentials if login is required, and submit. Many reviews finish within a day or two, but timing varies. Respond quickly if the reviewer asks questions.

If the app is rejected, read the explanation carefully. Fix the issue or reply in Resolution Center to clarify. Rejections are common for first submissions and are usually solvable.

Step 10: Release and monitor

You can release automatically, manually or on a scheduled date. A phased release rolls out gradually over several days for automatic updates, letting you catch problems early. After release:

• Watch crash reports and reviews in App Store Connect
• Track downloads and retention. See improving app retention
• Plan regular updates, including support for new iOS versions each year

Common reasons for rejection

• Crashes or bugs found during review
• Incomplete or inaccurate metadata and privacy information
• Missing demo account or review notes
• Guideline violations around payments, content or permissions
• Poor quality or minimal functionality

Checklist

• Developer Program membership active
• Bundle ID, capabilities and signing configured
• App built and tested on real devices
• Store listing, screenshots and keywords complete
• Privacy policy and App Privacy details accurate
• TestFlight feedback addressed
• Review notes and demo credentials provided
• Release strategy chosen

Final thoughts

Treat App Review as part of your schedule, not a surprise. Read the guidelines early, keep your declarations honest and test on real devices. If you would like help taking an app from build to App Store, see our app development service, or contact us. Targeting Android too? Read how to publish on Google Play.