How to publish an app on the App Store: the full process
Enrol in the Apple Developer Program, create the app in App Store Connect, upload and test a build, complete the listing and privacy details, then submit.
By Sohail Hussain21 November 20266 min read
To publish an app on the App Store you enrol your company in the Apple Developer Program, create the app record in App Store Connect, upload a signed build made with the current Xcode, test it through TestFlight, fill in the product page and privacy details, add notes and a demo account for the reviewer, and submit. As of October 2026 the program costs US$99 a year, Apple reviews most submissions within a day or two, and a first-time submission takes one to two weeks end to end once the app is ready, including a likely rejection to fix.
The steps below are in the order we run them. Steps one and two can start on the first day of the project; the rest happen in the final weeks.
What do you need before you start?
- A legal entity with a D-U-N-S number. Apple uses D-U-N-S to verify organisations. Apple's enrolment page has a free lookup and request tool; a new number can take several days.
- A website on your company's domain, with a privacy policy page and a support page or contact address. Both URLs are required on the listing.
- Someone with authority to sign for the company, who will accept Apple's agreements.
- The finished app, built with the Xcode version Apple currently requires, and a working backend the reviewer can reach.
If any of these is missing, sort it first. Our mobile app development projects open the store accounts in week one, in the client's name, for exactly this reason.
How do you set up the account and the app record?
Step 1: Enrol in the Apple Developer Program as an organisation
Enrol at the Apple Developer Program page with your company's details. Enrol as an organisation, not an individual: an individual account shows a person's name as the seller on the App Store, and cannot be shared with a team in the same way.
Apple verifies the organisation, the D-U-N-S record and the person enrolling, then asks for payment. Approval takes from a day to a few weeks. Once active, invite your developer as a team member with the Admin or App Manager role. Never hand over the Account Holder login.
Step 2: Create the app record in App Store Connect
In Certificates, Identifiers and Profiles, register the app's bundle ID, such as com.yourcompany.orders. It can never be changed once the app is live.
Then in App Store Connect, create a new app with its platform, name, primary language, bundle ID and an internal SKU. The name can be up to 30 characters and must be unique on the App Store, so create the record early to reserve it.
How do you build, upload and test the app?
Step 3: Build, sign and upload the app
Since April 28, 2026, uploads must be built with Xcode 26 or later against the iOS 26 SDK, according to Apple's upcoming requirements page. Apple raises this each spring, so check the page before your first upload.
The build is signed with a distribution certificate and a provisioning profile tied to the bundle ID, then uploaded from Xcode, Apple's Transporter app or a build service. For React Native apps built with Expo, EAS Build and EAS Submit handle signing and upload in two commands.
Each upload asks about encryption. If the app uses only standard HTTPS and the operating system's own encryption, it qualifies for the exemption, and you can declare that once in the app's Info.plist so the question stops appearing:
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
Set it to true instead if the app implements its own encryption, and complete the export compliance documentation.
Step 4: Test with TestFlight
Every uploaded build appears in TestFlight after processing. Up to 100 members of your App Store Connect team can install it straight away as internal testers. Up to 10,000 external testers can be invited by email or public link once the build passes a short Beta App Review. TestFlight builds expire after 90 days.
Give your own team two to four weeks of real use. The testers who find the most bugs are the staff who will support the app, using it for real work on their own phones.
What goes on the product page and the privacy label?
Step 5: Prepare the product page
On the version page in App Store Connect, add:
- Screenshots. At least one, and up to ten, for each device size App Store Connect marks as required: currently one iPhone size, plus a 13-inch iPad set if the app runs on iPad. Apple's screenshot specifications list the pixel sizes. Screenshots must show the real app.
- Text. A subtitle (30 characters), a description, a keyword field (100 characters, comma-separated) and promotional text you can change without a new version.
- URLs. Support URL and privacy policy URL. Our privacy policy generator gives you a starting draft; have a lawyer review it if you handle health, financial or children's data.
- App icon. A 1024 by 1024 pixel icon included in the build itself. Our app icon generator produces it and every smaller size from one image.
- Category, age rating and pricing. Answer the age rating questionnaire honestly (Apple revised it in 2025), set the price or "free", and choose the countries.
If you distribute in the European Union, you must also declare your trader status under the Digital Services Act; traders' contact details appear on the EU product page.
Step 6: Complete the privacy details
Under App Privacy, declare every type of data the app and its third-party SDKs collect, whether it is linked to the user and whether it is used for tracking. This becomes the privacy label on your product page.
Be precise. A label that says "no data collected" on an app with analytics, crash reporting and sign-in is a common reason for rejection, and later for removal. Check each SDK's documentation, and include the privacy manifests Apple requires for listed SDKs. If the app tracks users across other companies' apps or websites, it must ask permission through App Tracking Transparency.
How do you submit the app and release it?
Step 7: Add review notes and a demo account, then submit
In App Review Information, give the reviewer:
- A demo account with data in it, that will still work on the day of review.
- Notes on anything not obvious: features behind a location, hardware the reviewer will not have, why the app needs each permission.
- A phone number and email for someone who will respond.
Then select the build and submit. Apple's App Review page says it typically reviews at least half of submissions in under 24 hours and 90 percent in under 48. If the app is rejected, the message cites a guideline; fix it and resubmit, or reply in App Store Connect if the reviewer misunderstood. App Store rejection reasons covers the common ones.
Step 8: Choose how to release
Pick one of three release options: release manually when you press the button, automatically on approval, or on a scheduled date. Manual release is safest for a first launch, because you can time it with your announcement.
For updates, use phased release. Apple rolls the update out over seven days to users with automatic updates, from 1 percent on day one to everyone on day seven, and you can pause it if crash reports climb. Pair it with crash reporting so you see problems on day one, not in the reviews.
The Android side follows a different but parallel process; see how to publish an app on Google Play. For where the store launch fits in the whole project, read the mobile app development guide.
Was this guide useful?