How to Publish an App on the Apple App Store
To publish on the App Store, enroll in the Apple Developer Program (99 USD per year; organizations need a D-U-N-S number), create the app record in App Store Connect, and upload a build made with the current required Xcode and SDK (since April 2026, Xcode 26 or later). Complete the listing, screenshots, privacy details and age rating, test through TestFlight, then submit for App Review. Most reviews finish within a few days; rejections usually cite a specific guideline you can fix and resubmit.
- Enroll as an organization, not an individual, if the app belongs to a business; it controls the seller name shown on the store.
- Since April 28, 2026, uploads must be built with Xcode 26 or later using the iOS 26 SDK family.
- App privacy details are mandatory and must match what the app and its SDKs actually collect.
- Apps that let users create accounts must also let them delete the account from within the app.
- Give reviewers a working demo account and clear notes; missing access is a common reason for rejection.
The Steps
- Enroll in the Apple Developer ProgramEnroll as an organization with a D-U-N-S number, a legal entity name and a working website on your own domain. Verification can take several days, so start before development finishes.
- Create the app in App Store ConnectRegister a bundle ID, then create the app record with its name, primary language, SKU and category. Reserve the name early, since names must be unique on the store.
- Build with the required toolchainArchive the app in the currently required Xcode version and SDK, sign it with your distribution certificate, and upload it through Xcode or Transporter. Fix any processing warnings.
- Test with TestFlightDistribute the build to internal testers, then to external testers after a short beta review. Collect crash reports and feedback, and test on older and newer devices.
- Complete the product pageAdd screenshots for required device sizes, a description, keywords, support and marketing URLs, and a privacy policy URL. Describe what the app does today, not planned features.
- Fill in privacy and age ratingAnswer the App Privacy questionnaire for the app and every third-party SDK, and complete the age rating questions. Inaccurate privacy labels can lead to rejection or removal.
- Submit for App ReviewChoose the build, add review notes and a demo account with sample data, and explain any features that need hardware or location. Then submit and watch for messages in App Store Connect.
- Release and monitorRelease manually, automatically or as a phased rollout. Watch crashes, ratings and reviews during the first week, and reply to reviews from App Store Connect.
Getting the Account Right
The developer account decides whose name appears as the seller on the App Store. If a business owns the app, enroll the business as an organization. Apple requires the organization to be a legal entity that can sign contracts (it does not accept DBAs or trade names), to have a D-U-N-S number so Apple can verify identity and address, and to have a public website on a domain associated with the organization. The person enrolling must have authority to bind the company.
Two practical tips. First, start enrollment early, because D-U-N-S lookups and verification calls add days. Second, if an agency is building the app, have them work inside your account as a team member. Publishing under a developer's personal account makes it painful to take ownership later. Our page on who owns the code covers the contract side.
Nonprofits, accredited educational institutions and government entities can request a fee waiver if they meet Apple's criteria.
Set up roles before the first upload
App Store Connect has user roles such as Admin, App Manager, Developer, Marketing and Finance. Keep the Account Holder role with a company owner, give your developers only the access they need, and add your accountant to the Finance role so tax and banking forms are completed before launch. Paid apps and in-app purchases cannot go live until the Paid Applications agreement, tax forms and banking details are accepted, and that paperwork is a frequent last-minute delay.
Technical Requirements That Change Every Year
Apple periodically raises the minimum toolchain for new uploads. As of April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26 or the matching platform. Existing apps stay on the store, but your next update must meet the new rule. Check Apple's upcoming requirements page each spring, and confirm that any cross-platform framework you use (React Native, Flutter, Expo, Capacitor) supports the required Xcode before your release window.
Also plan for:
- Privacy manifests and required-reason APIs for your app and third-party SDKs.
- Sign in with Apple or an equivalent privacy-focused option if you offer third-party social login, subject to the exceptions in the guidelines.
- In-app account deletion whenever users can create an account.
- Permission prompts with clear purpose strings that explain why you need location, camera or contacts.
Passing App Review the First Time
App Review checks your app against the App Store Review Guidelines. The most common avoidable rejections are:
- Crashes or broken links found during review. Test the exact build you submit.
- No way to log in. Provide a demo account with realistic data, and note any feature that is region-locked or needs special hardware.
- Incomplete or misleading metadata, including screenshots that show features the app does not have, or placeholder text.
- Minimum functionality: an app that is just a wrapped website with little native value is often rejected.
- Payments: digital goods and subscriptions have specific in-app purchase rules, while physical goods and services must use other payment methods. US storefront rules on external purchase links changed in 2025 and 2026, so read the current version. See how to accept payments in an app.
If you are rejected, the message cites the guideline. Reply in the Resolution Center with questions, fix the issue, and resubmit. You can also appeal if you believe the reviewer misunderstood the app. Our page on why apps get rejected covers more cases.
Release Options and the First Week
After approval you can release immediately, schedule a date, or hold the build and release it manually. For updates, a phased release rolls out automatic updates to a growing share of users over seven days, and you can pause it if crash rates jump. Pair launch with basic App Store optimization: a clear subtitle, keyword field choices and screenshots that show outcomes, not menus. Read what ASO is for the basics.
Plan the week after launch as part of the project: someone should watch crash reports, respond to reviews and have a hotfix build ready. First-week ratings stick, so a fast fix for an early bug is worth more than a new feature.
Sources and Further Reading
We link to the primary documentation so you can verify the details yourself.
- Apple Developer Program enrollment, Apple Developer
- App Store Review Guidelines, Apple Developer
- Upcoming requirements, Apple Developer
- App privacy details on the App Store, Apple Developer
- App Store Connect Help, Apple Developer
- TestFlight, Apple Developer
Related Questions
How long does App Review take?
Apple does not promise a fixed time, but most submissions are reviewed within a few days, and many within a day. New apps, apps in sensitive categories and those needing extra information can take longer. Submit at least a week before any marketing launch date so you have room for a rejection and resubmission.
Can I publish under my agency's account?
You can, but it is a poor idea for a business. The agency's name appears as the seller, and moving the app later requires an app transfer that has conditions and can disrupt some services. Create your own organization account and add the agency as team members with limited roles.
Do I need a privacy policy?
Yes. Every app needs a privacy policy URL in App Store Connect and an accessible link within the app. It must describe what data you collect, how you use it and how users can request deletion. Have a qualified professional review it if you handle health, financial or children's data.
Can I test with real users before launch?
Yes. TestFlight lets you invite internal team members and external testers by email or a public link. External builds go through a brief beta review first. It is the best way to catch device-specific bugs and confusing flows before App Review and public ratings.