How to Submit an App to the Apple App Store: A 2026 Step-by-Step Guide

Short answer: to submit an app to the Apple App Store you need a paid Apple Developer Program membership, an app record in App Store Connect, a build made with the current Xcode and iOS SDK, complete store metadata (screenshots, description, privacy details, age rating), and a reviewer-ready test account. You then press Add for Review, wait for App Review (Apple says it typically handles about half of submissions within 24 hours and 90% within 48 hours) and choose when the approved version goes live.

That is the whole process in one paragraph. The rest of this guide walks through each step in the order you will actually do it, with extra notes for people who built their app on a no-code platform, because a few Apple rules apply to you in a very specific way. If you are publishing on Android too, keep our Google Play publishing guide open in another tab: the two stores ask for similar assets but in different formats.

Step 1: Enrol in the Apple Developer Program (under your own name or company)

You cannot publish on the App Store without an Apple Developer Program membership. It costs US$99 per year in most countries and you can enrol as an individual or as an organisation. Fee waivers exist for eligible non-profits, accredited schools and government bodies in some countries.

• Individual: fastest route. Your personal name appears as the seller on the App Store.
• Organisation: your business name appears as the seller. Apple asks for a D-U-N-S Number (a free business identifier from Dun & Bradstreet), a legal entity and a website, so allow extra days for verification.

Why this matters for no-code builders: App Review Guideline 4.2.6 says apps created from a commercial template or app generation service are rejected unless they are submitted directly by the provider of the app's content. In plain terms, the developer account should belong to your business, not to the agency or app-builder platform. Most no-code tools support this by asking you to connect your own Apple account or App Store Connect API key.

Step 2: Check the technical requirements before you build

Apple raises its minimum requirements regularly, and an outdated build is rejected at upload, before a human ever sees it. According to Apple's upcoming requirements page:

• Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 (or matching platform) SDK.
• Since September 9, 2026, iOS and iPadOS apps must target iOS 13 or later.
• Since January 31, 2026, every app must answer Apple's updated age rating questions before you can submit updates.

If you use a no-code builder, ask (or check its changelog) whether its iOS build pipeline already uses Xcode 26. If it does not, no amount of metadata polishing will get your app through.

Step 3: Create the app record in App Store Connect

Sign in to App Store Connect, open Apps and click the plus button to add a new app. You will need:

• Platform: iOS (add iPadOS later if your app supports tablets).
• App name: up to 30 characters. It must be unique on the store, so have a second option ready.
• Primary language.
• Bundle ID: the unique identifier of your app, for example com.yourbusiness.app. It has to match the build you upload, and it cannot be changed once the app is live.
• SKU: an internal reference only you see.

Step 4: Upload your build and test it with TestFlight

Developers upload builds from Xcode or Apple's Transporter app; most no-code platforms do it for you once your account is connected. After processing, the build appears under the TestFlight tab.

Use it. Install the app on at least one real iPhone through TestFlight and go through every screen the way a stranger would. Internal testers (people on your App Store Connect team) can test immediately. External testers, such as a few loyal customers, need a short beta review first. This is where you catch the crashes, broken links and empty screens that cause the most rejections.

Step 5: Fill in the product page metadata

This is the part people rush, and it is also what Apple reviewers and future customers read first. For each version you provide:

• Subtitle (30 characters) and keywords (100 characters). These drive search on the store; our beginner's guide to App Store Optimization shows how to choose them.
• Description that matches what the app actually does today. Do not describe features that are "coming soon".
• Screenshots: Apple's screenshot specifications require at least one screenshot for an iPhone with Dynamic Island, plus a 13-inch iPad set if your app runs on iPad. You can upload up to 10 per size as JPEG or PNG, without transparency. Show real screens from your app, not a marketing collage.
• Support URL and privacy policy URL. A privacy policy is required for every app.
• App Privacy details (the "nutrition label"): what data you collect, such as email, location, purchase history or analytics, and whether it is linked to the user. Include data collected by third-party tools inside your app, like analytics or payment SDKs.
• Age rating questionnaire and category.

Step 6: Give the reviewer everything they need

In the App Review Information section, add a working demo account (username and password) if any part of your app needs a login, a phone number and email where Apple can reach you, and short notes explaining anything that is not obvious. For a restaurant app, for example: "Orders placed with the demo account are test orders and are not sent to the kitchen." Apple's own App Review page warns that missing review information delays the review or causes a rejection.

Step 7: Submit, then choose how the release goes live

Select the build for the version, click Add for Review and then submit. The status moves from Waiting for Review to In Review and finally to approved or rejected. Before submitting, choose a release option:

• Automatic: live as soon as it is approved.
• Manual: you click release yourself. This is the best choice if you want to time it with a launch announcement or a menu change.
• Scheduled: live on a date you pick, but not before approval.

For later updates you can also turn on a phased release, which rolls the update out to automatic-update users gradually over seven days and can be paused if something goes wrong.

The rejections no-code apps hit most often

Guideline 4.2: Minimum functionality

Apple rejects apps that are basically a repackaged website. If your app is only a web view of your site, add things a browser cannot do well: saved favourites, ordering with order history, loyalty points, bookings, or useful push notifications. Our comparison of mobile apps and websites covers which features justify an app.

Guideline 4.3: Spam and copycat apps

Submitting several near-identical apps (one per branch, for example) is treated as spam. Use one app with a location picker instead.

Guideline 2.1: App completeness

Crashes, unfinished screens with dummy filler text, dead buttons and test data all lead to fast rejections. Your TestFlight pass in Step 4 is the fix.

Guideline 5.1.1(v): Account deletion

If users can create an account in your app, they must also be able to start deleting that account from inside the app. An "email us to delete" note is not enough.

Payments in the wrong place

Digital content and subscriptions unlocked inside the app generally have to use Apple's in-app purchase system. Physical goods and real-world services, such as food orders, salon appointments or event tickets, can use a normal payment provider. Our guide on adding payment processing to your app explains the difference. If you do sell digital items, Apple's Small Business Program lowers the commission to 15% for developers earning up to US$1 million a year.

What to do if your app is rejected

Rejections are normal, especially for a first app, and they are not a ban. The message in App Store Connect quotes the guideline number. Fix the issue, reply in the same thread to explain what changed, and resubmit. If you believe the reviewer misunderstood the app, reply with clear steps or a short screen recording before you change anything. Keep every reply factual and polite.

Quick pre-submission checklist

• Developer account in your business's name, membership active
• Build made with Xcode 26 or later, targeting iOS 13 or later
• Tested on a real iPhone through TestFlight: no crashes, no placeholder content
• Screenshots for iPhone with Dynamic Island (plus iPad 13-inch if supported)
• Privacy policy URL, App Privacy answers and age rating completed
• Demo login and reviewer notes added
• In-app account deletion if the app has accounts
• Release option chosen: automatic, manual or scheduled

Once you are approved, the real work starts: getting the app in front of your customers. Our app launch checklist for small businesses covers the first 30 days after you go live.

FAQ

How long does App Store review take?

Apple says it typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours. First submissions and apps with missing review information can take longer, so do not plan a launch for the day after you submit.

Can I publish an iPhone app without a Mac?

Uploading a build normally needs Xcode or Transporter on a Mac. Many no-code builders compile and upload the build on their own servers using your App Store Connect API key, so you can manage the listing from App Store Connect in any browser.

Do I need to pay Apple every year?

Yes. The Apple Developer Program membership renews annually. If it lapses, your apps are removed from sale until you renew.