The Apple App Store Review Process: What Publishers Need to Know
Publishers
Mar 1, 2026
Why App Store Review Matters for Publishers
For publishers launching a branded reading app on iOS, Apple's App Store review process is one of the most consequential — and least understood — parts of the launch timeline. A rejected submission can delay a launch by weeks. A misunderstood policy can result in an app being removed from the store after it is already live.
Understanding how the review process works, what reviewers look for, and where publisher apps most commonly run into problems is essential preparation for any iOS launch.
How the Review Process Works
When a new app or an app update is submitted to the App Store, it enters a review queue. Apple's review team — a combination of automated tools and human reviewers — evaluates the submission against the App Store Review Guidelines. Review times vary: Apple states that most submissions are reviewed within 24 hours, but complex apps or those flagged for additional scrutiny can take longer.
If the app is approved, it becomes available on the App Store. If it is rejected, the developer receives a message explaining the reason, and the submission must be revised and resubmitted. There is no limit to the number of times an app can be resubmitted, but each cycle adds time to the launch timeline.
The Reader App Guidelines
Publisher reading apps fall into a specific category that Apple treats differently from most other apps: "reader apps." Apple defines a reader app as one that allows users to access previously purchased content or content subscriptions — ebooks, audiobooks, magazines, newspapers, and similar digital content.
The key policy for reader apps is that they are permitted to exist on the App Store without offering in-app purchase for their content, provided they do not include a link or button that directs users to an external website to purchase. This is a specific carve-out from Apple's standard in-app purchase requirement, and it is important to understand its boundaries.
If a publisher's app allows users to purchase content within the app, that purchase must go through Apple's in-app purchase system, and Apple takes a commission (15% for subscriptions after the first year, 30% for one-time purchases for most developers). If the app does not offer in-app purchase at all — users purchase elsewhere and access their content through the app — the app can be approved as a reader app without Apple taking a commission, but it cannot include a link to the purchase page.
Common Rejection Reasons for Publisher Apps
Publisher reading apps are rejected for a predictable set of reasons:
External purchase links: Including a "Buy" button or link that directs users to a web store violates the reader app guidelines. The app can tell users that purchases are available elsewhere, but cannot link directly to the purchase page.
DRM issues: Apps that use DRM systems not approved by Apple, or that implement DRM in ways that interfere with Apple's own content protection systems, can be rejected.
Metadata mismatches: The app's description, screenshots, and functionality must be consistent. An app described as a reading app that also includes features not mentioned in the submission can trigger additional scrutiny.
Accessibility failures: Apple increasingly enforces accessibility requirements. Apps that do not support VoiceOver correctly, or that have text contrast issues, may be rejected.
Incomplete functionality: Submitting an app with placeholder content, broken features, or login screens that reviewers cannot get past will result in rejection.
The Review Account
Apple's reviewers need to be able to test the app's full functionality. For a reading app, this means they need a test account with content already loaded. Publishers must provide a demo account with credentials in the submission notes, and that account must have accessible content that demonstrates the core reading experience.
If the app requires a publisher-specific login (SSO, a specific domain email, or a licence code), the submission notes must explain this clearly and provide working credentials. Reviewers who cannot access the app's functionality will reject the submission.
Working with a Platform That Knows the Process
One of the practical advantages of using a specialist platform like Publish360 is that the App Store review process is a known quantity. The platform has been through review many times across multiple publisher apps. The DRM implementation, the in-app purchase flow, and the reader app configuration are all set up correctly from the outset — reducing the likelihood of rejection and shortening the time to approval.
If you are planning an iOS launch for a branded reading app, speak to the Publish360 team about how we manage the App Store submission process. See also: Launching a Branded Reading App: A Week-by-Week Guide and Why a Specialist Platform Beats a General App Agency.
