Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
To join the App Experience Program, app titles must meet the following requirements. These requirements will be updated regularly with reasonable notice to the developer.
A. Developers must publish titles in all required form factors at optimal quality (as defined in the requirements below). Required form factors will vary based on the application category, which will be published as part of the software requirements, as form factor limitations will reduce the quality experience on that form factor (e.g., video playback on the watch), except for certain devices where there is no viable technical solution to provide a high-quality experience due to system limitations (e.g., memory, performance, storage, input, or operating system version). When an Application Title is published in the App Experience Program on one of these additional form factors, the maximum Service Charge Rate specified in Section 9 will apply to such Application Title in that form factor.
I. Stability: Frame rate stability, crash rate, ANR, memory usage limits, data junk thresholds
secondly. Quality: Use Jetpack Compose (or an equivalently capable alternative) to deliver a high-quality app experience across all form factors (providing the same capabilities, e.g., adaptive design, edge-to-edge display, dynamic coloring and themes, and basic profiles)
Third. If a design system other than Android is supported, the Android equivalent must also be integrated (e.g. Material UX, System Emoji, Physics-Based Motion)
Fourth. Maintain the latest Android OS standards (e.g. 16K, predictive back navigation, app functionality)
v. New titles must be available on the following form factors: mobile, large screen (tablet, Android PC), XR (with titles playing in a 2D window on the
VI. Implement category-specific quality requirements as defined in the software (e.g. CameraX and Photo Picker integration for social apps, Cast for M&E, etc.)
for. Developers must deliver a consistent app experience by meeting experimental standards across apps, including:
I. For apps that support user sign-in, you can restore entitlement and sign-in (for example, View Sign in with Google, Restore Credentials API). For the avoidance of doubt, none of these requirements will preclude the use of other identification systems.
secondly. Engage SDK integration (for supported classes)
Third. Maintain feature parity between Android and similar non-Android platforms within 3 weeks of feature availability on any comparable platform, unless the feature is not enabled on the Android platform. For the avoidance of doubt, unequal benefits prior to entry into the program does not preclude eligibility for the program.
Fourth. Support content discovery experiences in Play by providing metadata and assets as required for the content vertical (e.g., Comics to Comics hub in Play, Drama Shorts). The specifications are specified for each sector and do not require the developer to incur any significant costs