Guide · 8 min read
Google Play Apps Experience Program: How to Qualify for 15% Commission in 2026
Google Play's Apps Experience Program (AEP) is the clearest revenue lever available to Android developers right now: qualify, and your commission on new-install transactions drops from 30% to 15% — a reduction that compounds meaningfully once your app generates regular paid conversions. Google has published the complete guideline checklist, and enrollment opens September 30, 2026. Here's what you actually have to implement, which requirements don't apply to your app, and how to evaluate whether the engineering investment earns back its cost at your current install volume.
What the Apps Experience Program actually does to your earnings
The Apps Experience Program restructures Google Play's service fee into two tiers based on install recency. Participating apps pay 15% on transactions from new installs and 20% on transactions from existing installs — compared to the standard 30% that applies without enrollment. Billing fees are excluded from both rates.
For most subscription apps, the largest share of revenue comes from existing users who are already installed. That cohort pays 20% under AEP versus 30% without it — still a meaningful reduction. For apps with strong top-of-funnel conversion, the 15% new-install rate is the bigger lever. Either way, both rates are lower than 30%, and the question is whether the qualification cost is worth the reduction. The program is available in the US, UK, EEA, and Australia starting September 30, 2026.
The structure differs meaningfully from Google Play's previous first-year 15% discount, which automatically dropped the rate for the first \$1M in annual developer revenue and then reverted to 30%. AEP is permanent for qualifying apps — not time-limited — making the qualification work a one-time investment. For context on how the Play Store commission landscape shifted overall in 2026, see the Google Play billing changes guide, which covers the broader post-Epic ruling changes including third-party payment processors.
AEP guideline categories: three themes, not all of which apply to your app
Google organizes AEP requirements around three themes: Quality & User Experience Foundations, Platform Integrations, and Play Content. Not every guideline applies to every app — applicability depends on your app's core use cases and the form factors it supports. A single-platform productivity app will face a shorter checklist than a media app targeting phone, tablet, TV, and Wear OS simultaneously.
This is the most important thing to understand before estimating the effort: filter for applicability first, not the full guideline list. Google evaluates apps against the guidelines that match their declared functionality. If your app has no media playback, the Media3 requirement doesn't apply. If it has no camera feature, CameraX is out of scope. The requirements that remain after this filter are the real scope — and for many apps, that filter removes the most complex integrations entirely.
The three themes cover: foundations (authentication, crash-free rate, data privacy practices), platform integrations (form-factor support for TV, Auto, Wear; media libraries; camera access), and Play content requirements (store listing accuracy, policy adherence, complete assets). Verification combines automated checks against your APK with a manual review by Google's team. Submitting through Play Console after September 30, 2026 triggers both in a single compliance submission.
Passkeys and SSO: the one authentication requirement every app must hit
Every app that includes sign-in must implement Passkeys or an approved SSO provider — this is the single Quality & UX Foundations requirement that applies across all app categories with authentication. Passkey-based sign-in eliminates phishing-susceptible password flows and reduces friction for returning users, both of which directly affect retention and crash rates. Google Credential Manager is the recommended integration path for Android.
For apps already using Google Sign-In via the legacy API: the modern Credential Manager API is the required path. Firebase Authentication with Google Sign-In through Credential Manager satisfies the requirement. For most apps already on Google identity, this is a half-day migration. If you're on a custom username/password flow with no SSO at all, the effort is more significant and worth scoping before deciding whether to pursue AEP.
The passkey requirement gates everything else in the program — it's not waivable and has no alternative path. Apps that already complied with Google's April 2026 Play Store permissions policy update requiring the system contact picker and location button are often already partway through the same Credential Manager migration, since those APIs share the same modern identity stack.
Platform integrations: Media3, Photo Picker, CameraX — what actually applies
The platform integration requirements include: Media3 (for any app with audio or video playback), CameraX (for any app that captures media), Photo Picker (for any app that accesses the device photo library), Cast Support (for apps with content suitable for TV streaming), and form-factor optimizations for Wear OS, Android TV, and Android Auto.
Photo Picker is the integration most commonly missed and most broadly applicable — if your app lets users select photos or videos from their device for any reason (profile picture, document scan, social post), you must use the Android system Photo Picker instead of direct media store access. This was also required in Google's April 2026 permissions policy update, so many apps should already satisfy it. A single audit covers both AEP and the permissions policy simultaneously.
For form-factor requirements: TV, Auto, and Wear OS support are only required if your app declares support for those surfaces in its manifest. If you haven't declared them, the associated guidelines don't apply — but you also can't add a form-factor declaration without meeting the associated quality guidelines. Deciding to add Wear OS support purely to qualify for AEP is a product decision that deserves real user-need justification, not just a compliance checkbox.
How Play Console verification works and when to submit
The verification window opens September 30, 2026. Before that date, Google recommends using the AEP guidelines documentation on developer.android.com to self-assess and begin implementing requirements — the guidelines are published and stable now, so you don't have to wait for enrollment to open to start the work.
The submission flow: once enrollment opens, you submit through Play Console and trigger a compliance check that combines automated APK analysis (checking for API usage, target API level, and integration signatures) with a manual review. Google has not published exact review turnaround times, but build in lead time before the September 30 availability date if you want the rate card to apply from day one. Verification is not instantaneous.
One practical implication: if your app is already targeting API 36 — the August 31, 2026 Play Store deadline covered in the Android API 36 requirements guide — you've likely resolved many of the baseline technical requirements that AEP automated checks evaluate. The API update and AEP qualification are aligned work streams, not separate ones. Apps that delay the API 36 update are also delaying AEP eligibility.
Is the effort worth it? A direct answer at three revenue tiers
The effort is worth it if you have a subscription or paid app already generating meaningful monthly Play Store revenue and you can qualify without building features your users don't want. The commission reduction is permanent — it doesn't phase out at a revenue threshold — so the economics improve as your app grows. An app generating \$5,000/month in Play Store revenue saves roughly \$500/month by moving from 30% to 20% on existing-install transactions alone.
The effort is not clearly worth it if: your Play Store revenue is below \$500/month (the absolute dollar savings are small relative to implementation cost), your app requires significant feature investment to satisfy platform integration requirements that users don't actually want, or your authentication architecture makes the passkey migration a multi-sprint project. Ship those integrations when the product case supports them — AEP enrollment will follow.
The middle case is the most common for indie devs: you're likely already compliant on Photo Picker if you've kept pace with Play policy, you may already use Google Sign-In, and the remaining requirements are a focused audit plus targeted implementation. For a solo developer, a dedicated assessment sprint followed by a targeted implementation sprint is realistic — particularly when the API 36 update is already underway. On the question of which monetization model benefits most from a commission rate reduction, the guide on in-app purchase vs subscription earnings has the math.
Play Store listing quality: what AEP checks on the store side
AEP's Play Content requirements evaluate your store listing, not just your APK. This includes policy compliance, an accurate and complete listing, and a properly sized Play Store feature graphic — the 1024×500 asset that appears at the top of your listing and in editorial placements. Apps missing this asset or using a low-quality placeholder fail the Play Content requirement automatically.
A complete listing is defined as having at minimum: a feature graphic, at least two screenshots, an accurate description, and a content rating. Screenshots are also evaluated qualitatively for accuracy — if your screenshots show features your app doesn't have, that's a compliance issue. Verify your current Play Store screenshot dimensions and ensure each frame reflects the app's current state. Screenshots from a significantly older version of the app are the most common listing quality flag Google surfaces during review.
The store listing audit is worth doing independently of AEP enrollment, since Play Store listing quality affects both discoverability and the retention-focused ranking signals Google emphasized in its 2026 search algorithm update. A cleaner listing with accurate screenshots reduces uninstall rates — and uninstall rates now negatively affect organic search placement on Play.
Self-assess now, submit September 30
The AEP verification window opens September 30, 2026. The complete guidelines are public now on developer.android.com — the self-assessment checklist is available today. For apps tracking toward API 36 compliance and Play policy adherence, the remaining gap to AEP qualification is often narrower than the full guideline list implies.
If your Play Store listing is missing a feature graphic or your screenshots need updating before AEP verification, AppsTemple's editor exports every required Play Store asset — feature graphic, screenshots at all required dimensions — in one pass.
Build your Play Store assets in the editor →
Frequently asked questions
what is the google play apps experience program?
The Google Play Apps Experience Program (AEP) is a quality program that reduces your Play Store service fee to 15% on transactions from new installs and 20% on transactions from existing installs — compared to the standard 30%. To qualify, apps must meet Google's integration and quality guidelines covering authentication, platform integrations, and store listing completeness. The program rate card becomes available starting September 30, 2026, in the US, UK, EEA, and Australia.
how do i qualify for the google play apps experience program?
Qualification requires meeting all AEP guidelines applicable to your app. Most apps must: implement secure sign-in via Passkeys or approved SSO (Google Credential Manager), maintain a complete and accurate Play Store listing with a feature graphic, and stay in policy compliance. Additional integrations (Media3, CameraX, Photo Picker, Cast, TV, Wear OS) apply only if your app supports those functions. Submit for verification through Play Console starting September 30, 2026.
does the 15% google play commission apply to all my transactions?
No. The 15% rate applies only to transactions from new installs. Transactions from existing installs — users who already have your app — are charged at 20%. Both are lower than the standard 30%, and both are permanent for qualifying apps. The previous first-year 15% discount was time-limited and automatic; AEP is permanent but requires qualification. Billing fees are excluded from both AEP rates.
what is the play store feature graphic and is it required for aep?
The Play Store feature graphic is the 1024×500 pixel banner shown at the top of your app's store listing and in editorial placements. A missing or low-quality feature graphic causes automatic failure of AEP's Play Content requirement. The correct dimensions are 1024px wide by 500px tall, PNG or JPEG format, with no alpha transparency. It's one of the most commonly overlooked listing assets for indie devs who submitted before the graphic became standard.
do i need android tv or wear os support to qualify for aep?
No — TV, Wear OS, and Android Auto support are only required if your app already declares support for those form factors in its manifest. If you haven't declared them, those guidelines don't apply. Adding a form-factor declaration solely to tick a box would require also meeting the full quality guidelines for that surface, so only pursue form-factor support if it genuinely benefits your users.