Preparing Documentation for App Store Review
You spent three months developing a clean SwiftUI app with async/await and configured StoreKit 2 for in-app purchases — but the reviewer rejects it under section 4.2 (minimum functionality). Why? They didn't understand how your product works. According to Apple's official guidelines, an app must demonstrate its value within 30 seconds. If the documentation doesn't explain non-trivial flows, rejection is guaranteed.
Our team has prepared documentation for 50+ projects, reducing typical review time by 3x compared to self-preparation and increasing approval chances to 95%. The average cost of a resubmission ranges from $200 to $500, and a 2–3 day delay can lose up to 10% of new users. Get a full package of documentation and forget about resubmissions.
What Does the Full Documentation Package Include?
App Review Information in App Store Connect is what the reviewer sees first. It requires:
- Test credentials with real access to features. If the app requires phone verification, provide a working number that receives SMS. Apple Sandbox accounts for in-app purchases must be configured and tested in advance.
- Notes for reviewer — a section developers ignore most often. Describe non-trivial flows: why the app requests background location, how to activate a paywalled feature, how a custom camera works.
- Demo video — for apps using CoreBluetooth, HealthKit, HomeKit, or NFC where the reviewer cannot physically test functionality without specific hardware. A video is mandatory.
Summary of required documents
| Document | Purpose | Required? |
|---|---|---|
| App Review Information | Instructions for the reviewer | Yes |
| Privacy Nutrition Label | Declaration of data collection | Yes |
| Age Rating | Age-based rating | Yes |
| Demo Video | Demonstration of hardware interaction | If applicable |
Privacy Nutrition Label is filled separately and must accurately reflect the app's actual behavior and all SDKs used. A mismatch between declared and actual data traffic is a common reason for rejection under Privacy guidelines. We audit every integrated framework: Firebase Analytics, Amplitude, AppsFlyer, and others collect data by default.
Age Rating is calculated via a questionnaire — an incorrectly set rating leads to rejection if the app's content doesn't match it.
How to Prepare Documentation in 2 Days?
- App audit: analyze code, configs, entitlements. Check compliance with current guidelines.
- Fill Privacy Nutrition Label: declare all collected data and SDKs used.
- Write reviewer notes: describe non-trivial flows, explain non-obvious permission requests.
- Create test accounts: with real access, verify one hour before submission.
- Final check: demo video, links, consistency.
Why Are Test Accounts the Main Reason for Rejection?
The most common issue: the test account doesn't work at review time — expired, token outdated, backend error. The reviewer sees a login screen and can't proceed — rejection under 2.1 (App Completeness). According to our statistics, 80% of rejections are due to documentation flaws, half of those because of non-working accounts. We check the account one hour before submission and use long-lived tokens.
Typical Documentation Failures
The second most common pitfall: the app requires external hardware (BLE device, NFC tag, specific QR code) and there's no video or explanation. The reviewer is not obligated to guess. For example, one client — a smart home app using CoreBluetooth — was rejected due to missing demo video. We added a video and notes, and the app passed review on the next submission.
Third, usage of camera or microphone outside an obvious context is not documented. If the app isn't a messenger or video editor but has audio recording somewhere for analytics, this must be explained in the notes.
What Is Included in Our Deliverables
Our comprehensive package includes:
- Privacy Policy and Terms of Use tailored to your app
- App Review Information with detailed notes for the reviewer
- Privacy Nutrition Label correctly filled
- Age Rating questionnaire completion
- Demo video recording for hardware-dependent apps
- Test account creation with long-lived tokens
- Training session on how to maintain documentation for future updates
- Support for up to three resubmissions if needed
How We Prepare Documentation
The package includes an app audit against current App Store Review Guidelines. We check all entitlements in Entitlements.plist and their correspondence with declared capabilities in App Store Connect. We write notes for reviewer covering every non-standard behavior.
Separately, we verify NSPrivacyAccessedAPITypes in PrivacyInfo.xcprivacy, mandatory since iOS 17 for certain system APIs including UserDefaults, FileTimestamp, SystemBootTime.
| Step | Duration | What We Do |
|---|---|---|
| App analysis | 1 day | Study code, configs, entitlements |
| Documentation audit | 0.5 day | Compare existing docs with requirements |
| Package preparation | 1 day | Write notes, compile Privacy Label, test |
| Final check | 0.5 day | Verify accounts, video, compliance |
Comparison: self-preparation typically takes 3–5 days with a 30–40% rejection rate. Our approach reduces it to 2 days and achieves up to 95% approval — twice as fast and more reliable. A prepared documentation package speeds up review by 3x: the reviewer immediately understands the app's logic. Over 50 successful submissions confirm the quality.
Get a consultation for your project — we'll analyze typical mistakes and prepare the documentation package. Order a turnkey documentation preparation and get approved on the first submission.