The process is well documented but has details that catch first-timers. In order:
- Enrol in the Apple Developer Program. It is an annual membership; Apple states the current price on its enrolment page. Individuals and organisations enrol differently, and organisations need extra verification.
- Create the app’s identity. An app identifier and the app record in App Store Connect, with the name, language and a bundle identifier that you cannot freely change later.
- Build and upload. Archive the app and upload it. TestFlight lets testers try it before review.
- Complete the listing. Description, keywords, screenshots for the required device sizes, category, age rating, support address and a privacy policy address.
- Declare privacy practices. The App Privacy section must describe the data your app and any third-party tools collect.
- Provide review information. If the app needs an account, give the reviewer a working demo login and notes.
- Submit and respond. Review usually returns questions or a rejection the first time for something small; fix and resubmit.
- Release. Manually, automatically, or on a date you choose.
What causes avoidable delay
- Missing or broken demo accounts.
- A listing that does not match what the app does.
- Not meeting the guidelines on account deletion, privacy disclosures or in-app purchases.
- Crashes on the reviewer’s device.
Read the App Review Guidelines early, and treat them as a checklist for design, not just for submission.