Development · Tip
App Store Approval Checklist
Practical rules and common rejection triggers for iOS App Store submissions
A concise checklist outlining common pitfalls and rejection triggers during Apple's App Store review process. It covers essential setup requirements around legal links, account deletion, social features, and reviewer communication to ensure initial approvals pass smoothly.
How it works
how to get approved on the app store (the caveman way)
- Apple approval is not hard. People overthink it or try to be clever. Apple wants apps that work, are honest, and are complete — not perfect.
- First rule: everything must be clear. No beta text, no "coming soon", no unfinished screens, no fake flows. v1 can be simple, but it must feel done.
- Your app must link to a terms of service and privacy policy. Real URLs, public pages, added both inside the app and in App Store Connect. Missing this alone gets you rejected.
- If you have subscriptions, set them up properly. Add them to the App Store listing, accept all business agreements, and be clear about pricing inside the app. For v1, don't do discounted or fake-urgency paywalls.
- If users create accounts, you must support account deletion inside the app. Not email-only, not "contact support" — actually inside the UI. Also don't force real names — use nicknames or usernames.
- If your app has any community, chat, or social features, users must be able to block and report others. No exceptions. Apple will reject you if this is missing.
- Make sure the app actually works. Test all flows, all buttons, all screens, especially on iPad 5th generation since reviewers often use it. Most rejections are just crashes or broken logic.
- Your App Store page must be honest. Explain what the app does clearly, show real screenshots of core features, and don't mention competitors or features you don't have yet.
- Don't use copyrighted content you don't own. Don't hide functionality. If you use AI or LLMs, add basic safeguards and be clear about how it's used.
- If reviewers need access, give them a test account and simple instructions. Screen recordings help a lot for complex flows.
- If you get rejected, respond fast and fix exactly what they say. Don't argue, don't overexplain, just comply.
Apple wants quality apps, not perfect ones.
What it's for
- Audit an iOS application before submitting it to App Store Connect
- Identify missing mandatory features like in-app account deletion or user reporting
- Prepare review notes, test accounts, and legal links for Apple reviewers
- Handle and resolve App Store review rejections quickly
Key points
- Eliminate placeholder elements: avoids beta labels, unfinished screens, and fake flows
- Mandatory legal links: guidelines on placing public ToS and privacy policies in-app and in Connect
- In-app account deletion: requires an in-UI deletion flow for apps with account creation
- UGC compliance: mandates block and report mechanisms for any social or chat features
- Testing recommendations: emphasizes testing against older devices like iPad 5th gen
- Reviewer preparation: instructions for providing working test accounts and demo recordings
- Rejection response protocol: guidance on complying directly with reviewer feedback
Pricing
Free
Details
- Type
- Tip
- Category
- Development
- Topic
- App Store Optimization
- Open source
- No
- Platforms
- iOS
- For
- iOS developers, mobile product managers, and indie hackers launching on the App Store
- Tags
- ios, app store, mobile dev, apple review, checklist, indie dev
Why it was saved
- @ErnestoSOFTWARE: Covers the concrete rejection triggers reviewers enforce: beta text, missing ToS/privacy policy, subscription setup, account deletion, block/report features, crashes on iPad 5th gen, honest store listings, copyright, test accounts, and how to respond to rejection.
Related
A repeatable playbook to validate app demand using ASO before writing code.
Open-source generator for App Store screenshots with 3D device mockups
A framework for validating app ideas using app store optimization before coding
Tactics for getting Model Context Protocol servers listed and recommended in Claude
Pre-submission compliance scanner for App Store and Google Play guidelines.
Deep-dive writeup and open-source release of the Apple Design Award–winning fitness tracker.
Updated