Essential Guidelines and Best Practices for Successful iOS App Submission

Submitting an iOS app to the App Store is more than uploading a build. Apple reviews functionality, metadata, privacy, and business model compliance. Use this guide as a practical checklist before you submit — it complements Apple’s official App Store Review Guidelines.

Before You Submit

Complete these steps in Xcode and App Store Connect before clicking Submit for Review:

1. Test on real devices — not only the simulator. Verify login, purchases, push notifications, and offline behaviour.
2. Archive a Release build — use a distribution certificate and provisioning profile matched to the App Store listing.
3. Fill App Store Connect completely — screenshots, description, keywords, support URL, privacy policy URL, and age rating questionnaire.
4. Declare privacy practices — App Privacy details in App Store Connect must match what your app collects (see App Privacy Details).
5. Provide review notes — include demo account credentials, hardware requirements, and steps to reach in-app purchase or login flows.

App Store Guidelines — Be Careful About Your Application

Apple rejects apps that are incomplete, misleading, or violate platform policies. Pay close attention to these areas:

Functionality and completeness

• Crashes, broken links, placeholder content, and “coming soon” screens in production builds are common rejection reasons.
• All advertised features must work in the build you submit.
• If your app requires login, provide a working demo account in App Review Information.

Accurate metadata

• App name, subtitle, description, and screenshots must reflect the actual app experience.
• Do not keyword-stuff or reference other platforms (e.g. “best Android app”) in iOS listing text.
• Preview videos and screenshots should use the correct device frame and locale.

Design and Human Interface Guidelines

• Follow Apple Human Interface Guidelines for navigation, typography, and platform conventions.
• Avoid copying another app’s UI or using non-standard controls that confuse users.
• Support current iOS versions and common screen sizes (including safe areas and Dynamic Type where applicable).

Legal and business requirements

• Apps that offer paid digital content or subscriptions must use In-App Purchase (StoreKit) unless an approved exception applies.
• Gambling, regulated industries, and health-related apps have additional documentation requirements.
• Include a privacy policy URL accessible from within the app and in App Store Connect.

In-App Purchase (IAP)

If your app sells digital goods, premium features, or subscriptions:

Requirement	What to do
Use StoreKit	Digital unlocks must go through Apple IAP — not external payment links for digital content consumed in-app.
Restore purchases	Provide a visible Restore Purchases action for non-consumable and subscription products.
Clear pricing	Show price and subscription terms before purchase; link to Terms of Use and Privacy Policy for auto-renewable subscriptions.
Test in Sandbox	Create sandbox tester accounts and verify purchase, renewal, cancellation, and restore flows.
Review notes	Tell reviewers how to reach the paywall and which sandbox account to use.

Read Apple’s In-App Purchase documentation and the Guideline 3.1 sections in the review guidelines.

Privacy, Permissions, and Data Collection

• Request permissions (camera, location, contacts, etc.) only when needed, with a clear purpose string in Info.plist.
• Use App Tracking Transparency (ATT) if you track users across apps or websites for advertising.
• Third-party SDKs (analytics, ads, crash reporting) must be disclosed in your privacy nutrition labels.
• Delete or export user data if your app stores personal information — align with applicable regulations (GDPR, etc.).

App Review Process — Practical Tips

1. Respond quickly if App Review requests changes or clarification in Resolution Center.
2. Increment build number when uploading a fixed binary — do not resubmit the same build after rejection.
3. Keep release notes concise — explain what changed for reviewers, not marketing copy.
4. Schedule release — choose manual release if you need coordinated marketing or backend readiness.
5. TestFlight first — run external beta through TestFlight to catch issues before App Store submission.