Implement specific quality standards to ensure a premium user experience across different hardware categories. This approach accounts for technical limitations, ensuring that stability benchmarks like Crash, ANR, and Jank are applied only to the intended device categories to maintain a high-quality ecosystem.
Required implementation
To qualify for AEP, your app must adhere to the following requirements:
Stability requirements:
Android vitals |
4GB+ RAM Android Devices |
|
<1% average crash rate |
<2% average crash rate |
|
<2% average ANR rate |
<3% average ANR rate |
|
<2% Excessive Slow Frames |
N/A |
To reduce volatility, these thresholds will be enforced based on the trailing 28 days of data considering only devices within the approved set for which your app has at least 1,500 sessions in the last 28 days.
Memory usage requirements:
To deliver a premium experience, Android 17 is introducing optimized memory handling and stricter platform requirements later this year–accompanied by new, actionable memory telemetry in the Play Console. Because meeting these standard memory limits will be required for the Apps Experience Program, we strongly encourage implementing these memory optimization strategies early to ensure app stability and a great user experience. More detailed compliance criteria to maintain your program status will be shared in the coming months.
Guideline applicability
This guideline applies to all apps that want to qualify for AEP across all form factors. There are no exemptions from this guideline.
Feature documentation and resources
The following resources provide implementation guidance for the Stability guideline. These resources are for your reference only and don't contain additional program requirements.
- Android Vitals - Diagnose and fix vital issues
- Managing your app's memory - Proactively reduce memory used by your app
Reference Device List
The following devices are used to test the AEP Stability guideline. Because Android hardware and features evolve, this list can be updated to ensure comprehensive coverage.
Device list
| Year | System on a Chip vendor |
System on a Chip model |
Manufacturer | Marketing name | Form factor |
|---|---|---|---|---|---|
| 2026 | TENSOR G5 | PIXEL 10 PRO XL | PHONE | ||
| PIXEL 10 PRO FOLD | FOLDABLE | ||||
| MEDIATEK | MT6993 | VIVO | X300 | PHONE | |
| X300 PRO | PHONE | ||||
| OPPO | FIND X9 PRO | PHONE | |||
| FIND X9 | PHONE | ||||
| QTI | SM8845 | ONEPLUS | ONEPLUS 15R | PHONE | |
| LENOVO | MOTOROLA SIGNATURE | PHONE | |||
| SM8850 | SAMSUNG | GALAXY S26 ULTRA | PHONE | ||
| GALAXY S26 | PHONE | ||||
| GALAXY S26+ | PHONE | ||||
| ONEPLUS | ONEPLUS 15 | PHONE | |||
| OPPO | FIND N6 | FOLDABLE | |||
| XIAOMI | XIAOMI 17 | PHONE | |||
| XIAOMI 17 ULTRA | PHONE | ||||
| LEITZPHONE POWERED BY XIAOMI | PHONE | ||||
| XIAOMI 17 PRO MAX | PHONE | ||||
| SAMSUNG | S5E9965 | SAMSUNG | GALAXY S26 | PHONE | |
| GALAXY S26+ | PHONE | ||||
| 2025 | TENSOR G4 | PIXEL 9 PRO XL | PHONE | ||
| PIXEL 9 PRO FOLD | FOLDABLE | ||||
| MEDIATEK | MT6991 | XIAOMI | XIAOMI 15T PRO | PHONE | |
| SAMSUNG | GALAXY TAB S11 | TABLET | |||
| GALAXY TAB S11 ULTRA | TABLET | ||||
| GALAXY TAB S11 ULTRA 5G | TABLET | ||||
| GALAXY TAB S11 5G | TABLET | ||||
| VIVO | VIVO X200 | PHONE | |||
| X200 PRO | PHONE | ||||
| X200T | PHONE | ||||
| OPPO | FIND X8 | PHONE | |||
| FIND X8 PRO | PHONE | ||||
| QTI | SM8735 | XIAOMI | XIAOMI PAD 8 | TABLET | |
| SM8750 | SAMSUNG | GALAXY S25 ULTRA | PHONE | ||
| GALAXY S25 | PHONE | ||||
| GALAXY S25+ | PHONE | ||||
| GALAXY S25 EDGE | PHONE | ||||
| GALAXY Z FOLD7 | FOLDABLE | ||||
| ONEPLUS | ONEPLUS 13 | PHONE | |||
| ONEPLUS 13S | PHONE | ||||
| PAD 3 | TABLET | ||||
| OPPO | FIND N5 | FOLDABLE | |||
| XIAOMI | XIAOMI 15 | PHONE | |||
| XIAOMI 15 ULTRA | PHONE | ||||
| SONY | XPERIA 1 VII | PHONE | |||
| VIVO | IQOO 13 | PHONE |
Comprehensive testing across every specific model may not be required because several devices in the list use identical SoCs and exhibit comparable performance. Developers are eligible to self-certify for the guidelines once they have successfully verified requirements on at least one device from each listed SoCs:
Phones
| Year | System on a Chip | Devices |
|---|---|---|
| 2026 | Tensor G5 | PIXEL 10 PRO XL |
| 2025 | Tensor G4 | PIXEL 9 PRO XL |
| 2026 | MTK MT6993 | X300, FIND X9 |
| 2025 | MTK MT6991 | XIAOMI 15T PRO, GALAXY TAB S11, VIVO X200, FIND X8 |
| 2026 | QCOM SM8845/8850 | ONEPLUS 15R, MOTOROLA SIGNATURE, GALAXY S26, ONEPLUS 15, XIAOMI 17 |
| 2025 | QCOM SM8750 | GALAXY S25, ONEPLUS 13, PAD 3, XIAOMI 15. XPERIA 1 VII, IQOO 13 |
| 2026 | Exynos S5E9965 | GALAXY S26 |
Tablet
| Year | System on a Chip | Devices |
|---|---|---|
| 2025 | MTK MT6991 | GALAXY TAB S11 |
| 2025 | QCOM SM8735 | XIAOMI PAD 8 |
| 2025 | QCOM SM8750 | OPPO PAD 3 |