How to submit an app to the App Store, step by step

Submitting looks like one button. It is really a checklist, and the button is the last item. Do the earlier items properly and the review tends to be quick. Skip them and you will be reading rejection emails.

Before you touch App Store Connect

• Test the actual app on a phone. Not just a simulator. Apple's guidelines say to test on-device for bugs and stability.
• Finish the product. No placeholder text, no empty screens, no dead links.
• Write the pages Apple requires. You need a support link with current contact details and a privacy policy.
• Decide your account model. If people can create accounts, plan in-app account deletion.

If you are not sure your app is ready, run a QA pass first. See how to QA test an AI built app.

The steps

1. Get your Apple developer account ready. Only the Account Holder can sign legal agreements. Banking changes made by other roles need the Account Holder's approval, and Apple requires your tax forms before it processes banking information. If you sell anything or have paid features, Apple has banking requirements you will need to complete.
2. Create the app record in App Store Connect. This holds your name, listing and versions.
3. Upload your build. Use Xcode or Apple's upload tools to send a build to App Store Connect.
4. Run it through TestFlight. TestFlight lets you send beta builds to up to 100 internal testers and up to 10,000 external testers. Apple says to keep distributing builds until issues are resolved before submitting. Read our TestFlight guide.
5. Finish the listing. Add your description, keywords, category, screenshots, privacy details and support link. Screenshots should show the real app in use.
6. Fill App Review Information. Add contact info and, if you have a login, a valid demo username and password. If features need special setup, explain it. Apple says missing details can delay review or cause a fail.
7. Select the build and submit for review. In the App Review area you can manage submissions and talk to the review team. Apple's submission overview explains the limits.
8. Watch status and reply. Apple emails you on status changes. You can also check the Apps section of App Store Connect or the iPhone app.
9. Release. Once approved you can release the version.

Rules worth knowing

• Each platform can have one app version submission under review at a time. You can also submit items like in-app events or custom product pages in a second submission.
• Submissions may not be reviewed in the order you send them.
• Beta testers, demos and trial versions belong in TestFlight, not on the App Store (guideline 2.2).
• If your app uses sign-in, guideline 5.1.1 says you must offer account deletion within the app.

How long it takes

Apple says at least 50% of submissions are reviewed in less than 24 hours and 90% in less than 48. Rejections reset that clock. That is why the pre-flight checks matter more than the submit button.

How we do it at SupaKid Studios

Tomi calls the submission process long and tedious, especially for a new vibe coder or solo founder. Filling forms, taking screenshots, writing the listing, then waiting through rounds of replies adds up. So he built a workflow where an AI browser agent does the form work.

The setup is simple. You open the Aside browser, sign into your Apple developer account, and give the agent access to the code repo. It can spin up its own simulator on your Mac and take screenshots, fill the forms, and research the store to find good listing wording. A daily routine checks for Apple's response. You still handle the parts that must come from the account owner, like tax forms and banking details. Apple's role pages explain what each account role can do.

We used this to get JetQuest Travel's group travel club app approved and live on the App Store. In our process the client approves what goes out, and we always report real status. "Submitted" and "approved" are different things.

Want the broader picture? Read how to get your app approved faster, then see how our iOS app team works.

Review notes that help

The App Review Information section is your chance to talk to the reviewer before they open the app. Use it well:

• Say in two sentences what the app does and who it is for.
• Give the demo login and say which screens to open first.
• Explain anything unusual, like a feature that needs special hardware or a setting. Apple says to be ready with a demo video if the environment is hard to replicate.
• Keep your contact details current so Apple can reach you quickly.

Short, honest notes beat long ones. They also give you a record to update when you resubmit.

What goes wrong

• Missing demo login, so the reviewer cannot get past the first screen.
• Screenshots from an old design.
• A privacy policy that does not match the real data the app collects.
• Submitting a build you never ran on a real device.
• Missing banking or tax setup when you have paid features.

Ready to ship?

If you have built the app and want a team to carry it to the App Store, book a 30-minute call with SupaKid Studios. We will tell you what is left and who does it.