App Store Submission and App Review

IOS Development 11 min min read Updated: Nov 16, 2026 Intermediate
App Store Submission and App Review
Intermediate Topic 5 of 5

What You Prepare

ItemNotes
App name (30 characters max)Short and memorable, include a keyword if natural
Subtitle (30 characters)One line benefit
DescriptionFirst lines matter most. Explain value, not just features
Keywords (100 characters)Comma-separated, no spaces, do not repeat words from the name
ScreenshotsRequired sizes for the largest iPhone (and iPad if supported). Show real app screens with short captions
App icon1024 x 1024 px, no transparency
Privacy Policy URLA public web page, required
Support URLA page or email form for users
Category and age ratingAnswer the questionnaire honestly
Names and sizes change: Required screenshot sizes and field limits are updated by Apple from time to time. Check the current App Store Connect Help page when you prepare your listing.

Privacy Details

Apple shows App Privacy labels. You declare which data your app collects (email, location, usage data, identifiers) and whether it is linked to the user or used for tracking. Include the data collected by any third-party SDK, such as analytics or ads.

  • If you track users across other companies' apps and sites, you must ask permission with the App Tracking Transparency prompt
  • Apps that let users create accounts must also let them delete the account from inside the app
  • Add a privacy policy that matches what the app really does

Submission Steps

  1. Upload a build (previous lesson) and wait until it is processed.
  2. Open your app in App Store Connect and create a new version.
  3. Fill in the listing text, keywords and screenshots.
  4. Select the build.
  5. Add App Review Information: contact details and, if your app needs a login, a demo account that works.
  6. Choose the release option: manual, automatic or scheduled.
  7. Click Submit for Review.
Review time: Most reviews finish within a day or two, but it varies. Plan ahead and do not schedule important launches too tightly.

Common Rejection Reasons

ReasonHow to avoid it
Crashes or bugsTest on real devices with the Release build, use TestFlight
Incomplete app or placeholder contentRemove 'lorem ipsum', dead buttons and broken links
Login without a demo accountGive reviewers working credentials in the review notes
Unclear permission textsExplain the user benefit
Misleading metadataScreenshots and description must match the real app
Minimum functionalityA simple website wrapper is not enough. Offer real app value
In-app purchases not used correctlyDigital content and subscriptions must use Apple's In-App Purchase system
Missing account deletion or privacy policyAdd both before submitting

If you are rejected, read the message in Resolution Center, fix the issue and reply or resubmit. Rejections are normal, even for experienced developers.

After Release

  • Watch crashes and feedback in App Store Connect > Analytics and Xcode Organizer
  • Answer reviews
  • Ship updates with a higher version or build number and What's New text
  • Use phased release for updates, so a bug does not reach everyone at once
Next step: Start with a small, polished app. A focused app with a clean design is better than a huge app with many unfinished features.

Conclusion

A strong listing, honest privacy answers, a working demo account and a stable build lead to a smooth review. Expect to learn from a first rejection.

Quick Summary: Prepare icon, screenshots, text and privacy details, submit the build with review notes and fix issues from Resolution Center.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators