What you need in place to submit
Publishing to Apple's App Store runs through App Store Connect, Apple's portal for managing your app. Before you can submit, you need an enrolled Apple Developer account, a finished build, and a complete store listing — Apple won't review an app with missing pieces.
The listing itself is part of what gets reviewed. Screenshots, description, and privacy details all have to be accurate, because misleading metadata is a common reason apps get sent back.
- An enrolled Apple Developer account (paid, annual, registered to you)
- The app set up in App Store Connect with its name and metadata
- Screenshots for the required device sizes and an app description
- A privacy policy URL and accurate App Store privacy labels
- A signed build uploaded and selected for submission
Apple's review process
Once you submit, human reviewers at Apple check your app against the App Store Review Guidelines. They test that it works, that sign-in functions, and that it does what the listing claims — which is why you provide demo login credentials for anything behind an account.
Apple's review is the stricter of the two major stores. A first rejection is common and isn't a crisis: Apple tells you specifically what to fix, you correct exactly that, and you resubmit.
- Human review against the published App Store Review Guidelines
- Provide demo/test credentials so reviewers can get past login
- Common rejections: crashes, broken features, misleading or incomplete metadata
- Privacy issues: undisclosed data collection or missing permission reasons
- Read rejection notes literally and fix precisely what's cited, then resubmit
Going live and staying compliant
After approval, you decide when the app goes public and can use a phased release to roll it out gradually while watching for problems. Publishing isn't a one-time event — every update goes through review again.
Staying published also means staying compliant. Apple updates its guidelines and requirements over time, and apps that fall behind can be pulled, so ongoing attention matters.
- You control the go-live timing once the app is approved
- Phased release lets you roll out to a percentage of users first
- Every future update goes back through App Store review
- Keep up with guideline and privacy-requirement changes over time
- Respond promptly if Apple flags an issue to avoid removal
More on ios apps
Frequently asked questions
How is publishing to the App Store different from just building the app?
Building is creating the app; publishing is getting Apple to accept it and make it available to download. Publishing has its own requirements — an App Store Connect listing, screenshots, privacy disclosures, and passing Apple's human review. Many first-time app owners underestimate this final stretch, which is why we treat it as its own phase.
Why do apps get rejected by Apple, and can it be avoided?
The most common reasons are crashes, broken sign-in, incomplete functionality, misleading store listings, and privacy gaps like undisclosed data collection. You can greatly reduce the risk by testing thoroughly on real devices, following the App Store Review Guidelines, and providing accurate metadata and demo credentials — but a first-time rejection still happens sometimes, and it's fixable.
Do I need my own Apple Developer account to publish?
Yes, and it should be registered in your name, not your developer's. That account owns your app on the App Store, so keeping it under your control means you keep control of the app, its listing, and its future updates. It's a paid annual enrollment with Apple, and we can walk you through setting it up on a free consultation.