What nobody tells you about shipping to the App Store for the first time
You built the app. It works on your phone. You're ready to ship. You open App Store Connect, fill out the forms, upload the build, and hit Submit.
Three days later, Apple rejects you.
This isn't a worst case. This is the median experience for first-time submissions. App Store Review is thorough, opinionated, and occasionally surprising. Knowing what they check before you submit saves you the round trip.
The rejection categories that catch everyone
Metadata rejections (Guideline 2.3)
Your app name, subtitle, description, and screenshots are reviewed independently from your code. Apple will reject you for:
- Mentioning a platform in the name. "MyApp for iPhone" isn't allowed.
- Using generic terms as the name. "Weather" won't pass if you aren't Apple.
- Screenshots that don't match the app. If your screenshots show features that aren't in the build you submitted, that's a rejection.
- Placeholder text anywhere. "Lorem ipsum" in a screenshot, a "coming soon" label in the app, a test email address in the description.
In-app purchase rejections (Guideline 3.1)
If your app charges for anything, the rules tighten:
- Every purchase must go through Apple's in-app purchase system. No linking to a website for payment. No mentioning that cheaper options exist elsewhere.
- Subscription descriptions must include the price, the duration, and the renewal terms. "Subscribe for $4.99/month. Subscription automatically renews unless auto-renew is turned off at least 24 hours before the end of the current period."
- Free trials must clearly state what happens when the trial ends.
- You need a Restore Purchases button. Apple will test it.
Privacy rejections (Guideline 5.1)
- A privacy policy URL is required. It must return a real page, not a 404.
- The App Privacy questionnaire must match reality. If your app collects email addresses, the questionnaire must say so. If your analytics SDK collects device identifiers, that counts too.
- Account deletion. If users can create an account, they must be able to delete it from within the app. This is enforced strictly.
Design rejections (Guideline 4)
Apple cares about quality. They will reject apps that:
- Crash during review. They test on devices you might not have tested on.
- Have obvious UI bugs. Buttons that do nothing, screens that don't load, text that overlaps.
- Are too simple. A single-screen app with no real functionality will be rejected as "not useful enough."
- Use non-standard UI in confusing ways. If your back button doesn't go back, that's a problem.
How to avoid the round trip
Test on real devices
The simulator doesn't catch everything. Test on the oldest device your app supports. Test on the newest device. Test with Dynamic Type set to the largest size. Test with VoiceOver on. Apple's reviewers do all of this.
Fill out every field in App Store Connect
There are a lot of fields. Most of them are required. The review contact information, the demo account credentials (if your app has login), the notes for the reviewer. Fill them all out. If your app requires a login, provide a test account that Apple can use.
Submit early, iterate after
Don't wait until launch day to submit. Submit a version two weeks early. If it gets rejected, you've time to fix it and resubmit. The review typically takes one to two days, but resubmissions after a rejection go back to the end of the queue.
Read the guidelines
The App Store Review Guidelines are long but readable. Sections 2, 3, and 5 are the ones that catch first-time submitters. Twenty minutes of reading saves you a week of waiting.
What we handle
When we build an app for a client, the App Store submission is part of the project. We fill out the metadata, prepare the screenshots in both color schemes for every device class, write the description, set up the in-app purchases, configure the privacy questionnaire, and submit the build. We've done this enough times to know where the surprises are.
The goal is a clean first submission. It doesn't always happen. Apple rejected one of our own Mac updates this year over a single trademarked word in the store subtitle; moving it to the description fixed it and the resubmission passed. The point is knowing where the surprises are before you hit Submit.