The Google Play Store Review Process for Publisher Apps: What's Changed in 2026 and How to Get Approved First Time
Publishers
Mar 12, 2026
Publishing a reading app on Google Play requires more preparation than most publishers expect. In February 2026, Google revealed it prevented 1.75 million policy-violating apps from being published in 2025, banned 80,000 developer accounts, and blocked 255,000 apps for requesting excessive access to sensitive user data. The review process is a substantive gatekeeping function — understanding what has changed is essential before you submit.
What Has Changed in 2026
Google has made three significant changes that directly affect publishers.
Mandatory closed testing. New developer accounts must complete a closed test with at least 12 testers for 14 consecutive days before publishing to production. This adds a minimum two-week runway to any launch timeline.
AI-enhanced data safety scrutiny. Google now uses generative AI models to identify policy violations more quickly. Apps whose Data Safety section disclosures do not accurately reflect actual data collection — including data collected by third-party SDKs — are far more likely to be flagged.
Play Policy Insights in Android Studio. A new pre-submission tool surfaces likely policy issues before you submit, catching the most common rejection triggers at development time.
Review Timelines
Scenario | Typical Timeline |
|---|---|
New app, clean submission | 24–72 hours |
New app with subscription billing or DRM | 3–7 days |
Complex SDK integrations or sensitive content | 7–14 days |
Resubmission after rejection | 3–7 days additional |
Build a minimum three-week buffer into any launch timeline: two weeks for closed testing, plus one week for the initial review.
Common Rejection Reasons for Publisher Apps
Permissions without justification. Every permission must have a clear, user-facing purpose described in the store listing and Data Safety section. Requesting permissions "just in case" is a fast route to rejection.
Inaccurate Data Safety disclosures. Google cross-checks declared data practices against actual app behaviour. Third-party analytics SDKs, advertising frameworks, and crash-reporting tools must all be audited and declared.
Billing policy violations. In-app subscriptions must use Google Play Billing. As of March 2026, the standard commission is 20% for purchases and 10% for subscriptions after year one. A direct billing option is available at 15%/5% but requires Google's approval.
DRM and entitlement flow issues. Readium LCP is fully compliant with Google Play policies. Widevine is Google's native standard for video. The most common issue is an entitlement verification flow that appears to bypass billing — ensure your licensing server is reachable from Google's review environment.
Google Play vs Apple App Store: Key Differences
Aspect | Google Play | Apple App Store |
|---|---|---|
Review time (first submission) | 3–7 days | 1–3 days |
Closed testing requirement | 12 testers × 14 days | TestFlight, no minimum |
Subscription fee (after year 1) | 10% | 15% |
Direct billing option | Available (with approval) | EU only |
DRM standard for video | Widevine | FairPlay |
Google Play is now meaningfully cheaper for subscription-based reading apps than the App Store after year one — a significant change as of March 2026.
How Publish360 Handles the Technical Requirements
For publishers on Eden Interactive's Publish360 platform, the technical requirements for Google Play submission are handled at the platform level. Readium LCP, Widevine, and Google Play Billing integration are all built in. The pre-submission checklist becomes a metadata and policy exercise rather than a technical one.
If you are planning a Google Play launch, contact the Eden Interactive team to discuss your timeline and requirements.
Related reading: The Apple App Store Review Process for Publisher Apps | App Store Monetisation for Publishers in 2026
