This checklist defines a set of core quality criteria and associated tests to help you assess the quality of your app. Some of these criteria might be easy to miss, and the tests help you remember to include them in your test plans.
The checklist highlights the minimum quality that all apps should meet. Your testing will likely go well beyond what's described here.
Each item in the quality checklist has a unique ID which you might find helpful to use when you communicate with your team.
Your app should provide standard Android visual design and interaction patterns where appropriate, for a consistent and intuitive user experience.
|The app supports standard Back button navigation and does not make use of any custom, on-screen "Back button" prompts.
|The app supports gesture navigation for going back / going to the home screen.
The app correctly preserves and restores user or app state.
The app preserves user or app state when leaving the foreground and prevents accidental data loss due to back-navigation and other state changes.
When returning to the foreground, the app should restore the preserved state and any significant stateful transaction that was pending. Examples include: changes to editable fields, game progress, menus, videos, and other sections of the app or game.
Notifications follow Material Design guidelines. In particular:
For messaging / social apps and conversations:
|UI and Graphics
|The app supports both landscape and portrait orientations (if possible).
Orientations expose largely the same features and actions and preserve functional parity. Minor changes in content or views are acceptable.
|The app uses the whole screen in both orientations and does not letterbox to account for orientation changes.
Minor letterboxing to compensate for small variations in screen geometry is acceptable.
|The app correctly handles rapid transitions between display orientations without rendering problems or losing state.
The app displays graphics, text, images, and other UI elements without noticeable distortion, blurring, or pixelation.
The app displays text and text blocks in an acceptable manner for each of the app’s supported languages.
|The app’s content, and all web contents referred to by the app, support dark theme.
Your app should implement the expected functional behavior.
|Audio resumes when the app returns to the foreground, or indicates to the user that playback is in a paused state.
|If audio playback is a core feature, the app should support background playback.
When the user initiates audio playback, the app should do one of the following within one second:
|The app should request audio focus when audio starts playing and abandon audio focus when playback stops.
|The app should handle other apps’ requests for audio focus. For example, an app might reduce playback volume when another app plays speech.
|If the app plays audio in the background, it must create a Notification styled with MediaStyle.
|If the app plays video, it should support picture-in-picture playback.
|If the app encodes video, it should do so using the HEVC video compression standard.
|The app should use the Android Sharesheet when sharing content. It can suggest targets that are unavailable to custom solutions.
|The app avoids running background services where possible. To ensure the smooth running of the user’s device, the system applies various restrictions on background services. These are not considered good uses of background services:
Learn how to choose the right solution for your work.
|The app properly supports the power management features that were introduced in Android 6.0 (Doze and App Standby). In the case where core functionality is disrupted by power management, only qualified apps may request an exemption. See Support for other use cases in Doze and App Standby.
Performance and stability
Your app should provide the performance, stability, compatibility, and responsiveness expected by users.
|The app does not crash or block the UI thread causing ANR (Android Not Responding”) errors. Utilize Google Play’s pre-launch report to identify potential stability issues. After deployment, pay attention to the Android Vitals page in the Google Play developer console.
|The app loads quickly or provides onscreen feedback to the user (a progress indicator or similar cue) if the app takes longer than two seconds to load.
|Apps should render frames every 16ms to achieve 60 frames per second. Developers can use the Profile HWUI rendering option in testing. If there are issues, tools are available to help diagnose slow rendering.
|With StrictMode enabled (see StrictMode Testing, below), no red flashes (performance warnings from StrictMode) are visible when testing the app. Any red flashes indicate bad behaviors regarding storage, network access, or memory leaks.
|The app runs on the latest public version of the Android platform without crashing or severely impacting core functionality.
|The app targets the latest Android SDK by setting the
|The app is built with the latest SDK by setting the
|Any third-party SDKs used are up-to-date. Any improvements to these SDKs, such as stability, compatibility, or security, should be available to users in a timely manner.
The developer is accountable for the entire app’s codebase, inclusive of any third-party SDKs used.
|The app does not use non-SDK interfaces.
|The app properly supports the power management features that were introduced in Android 6.0 (Doze and App Standby). In the case where core functionality is disrupted by power management, only qualified apps may request an exemption. During development, developers can test app standby and doze behavior using these ADB commands.
Privacy & security
Your app should handle user data and personal information safely, with the appropriate level of permission.
In addition to this checklist, applications published on the Google Play Store must also follow the User Data policies to protect users' privacy.
|The app requests only the absolute minimum number of permissions that it needs to support its use case at hand. For some permissions such as location, use coarse location in place of fine location if possible.
The app should only request permission to access sensitive data (such as SMS, Call Log, or Location) or services that cost money (such as Dialer or SMS) if it’s directly related to the core use cases of the apps. Implications related to these permissions should be prominently disclosed to the user.
Depending on how you are using the permissions, there might be an alternative way to fulfill your app's use case without relying on access to sensitive information. For example, instead of requesting permissions related to a user’s contacts, it may be more appropriate to request access by using an implicit intent.
|The app requests runtime permissions in context, when the functionality is requested, rather than upfront during app startup.
The app should design its UX to clearly convey why certain permissions are needed. If that’s not possible, it should follow the recommended flow to explain why a feature in your app needs a permission.
The app should gracefully degrade when users deny or revoke a permission. The app should not prevent the user from accessing the app altogether.
|Data & Files
|All sensitive data is stored in the app's internal storage.
|No personal or sensitive user data is logged to the system log or an app-specific log.
|The app should not use any non-resettable hardware IDs, such as the IMEI, for identification purposes.
|Provide hints to autofill account credentials and other sensitive information, such as credit card info, physical address, and phone number.
|Integrate One Tap for Android for a seamless sign in experience.
|Integrate biometric authentication to protect financial transactions or sensitive information, such as important user documents.
|Only application components that share data with other apps, or components that should be invoked by other apps, are exported.
Always set the
All intents and broadcasts follow best practices:
|All content providers that share content between your apps use
android:protectionLevel="signature" for custom permissions. This includes activities, services, broadcast receivers, and especially content providers.
Most apps should not rely on accessing a list of installed packages. The access has been restricted beginning in Android 11.
|All network traffic is sent over SSL.
|The application declares a network security configuration.
|If the application uses Google Play services, the security provider is initialized at application startup.
|All libraries, SDKs, and dependencies are up to date.
|No debug libraries are included in the production app. This can cause performance as well as security issues.
|Do not use setAllowUniversalAccessFromFileURLs() for accessing local content. Instead, use WebViewAssetLoader.
On Android 6.0 and above, use HTML message channels instead.
|The app does not dynamically load code from outside the app's APK. Developers should use Android App Bundles, which includes Play Feature Delivery and Play Asset Delivery.
Starting August 2021, the use of Android App Bundles will become mandatory for all new apps in the Google Play store.
|The app uses strong, platform-provided cryptographic algorithms and a random number generator. Also, the app does not implement custom algorithms.
Be sure that your apps can be published on Google Play.
|The app strictly adheres to the terms of the Google Play Developer Content Policy and does not offer inappropriate content, does not use the intellectual property or brand of others, and so on.
|The app maturity level is set appropriately, based on the Content Rating Guidelines.
|App Details Page
The app’s feature graphic follows the guidelines outlined in this support article. Make sure that:
|The app’s screenshots and videos do not show or reference non-Android devices.
|The app’s screenshots or videos do not represent the content and experience of your app in a misleading way.
|Common user-reported bugs in the Reviews tab of the Google Play page are addressed if they are reproducible and occur on many different devices. If a bug occurs on only a few devices, you should still address it if those devices are particularly popular or new.
Setting up a test environment
For the purpose of setting up a test environment for this checklist, we recommend the following:
- Focused on emulator testing - Android Emulator is a great way to test your app under different Android versions and screen resolutions. You should set up emulated devices (AVDs) to represent the most common form factors and hardware/software combinations for your target user base.
- Hardware devices - Your test environment should include a small number of actual hardware devices that represent the key form factors and hardware/software combinations that are currently available to consumers. It's not necessary to test on every device that's on the market — rather, you should focus on a small number of representative devices, even using one or two devices per form factor.
- Device test labs - You can also use third party services, such as Firebase Test Lab, to test your app on a wider variety of devices.
- Test with the latest Android version - In addition to testing representative Android versions for your target user base, you should always test against the latest version of Android (currently Android 11). This ensures that the latest behavior changes do not negatively impact your user’s experience.
For more comprehensive guidance on testing including unit testing, integration testing and UI testing, check out the Android testing fundamentals.
These test procedures help you discover various types of quality issues in your app. You can combine the tests or integrate groups of tests together in your own test plans. See the sections above for references that associate criteria with these test procedures.
Navigate to all parts of the app — all screens, dialogs, settings, and all user flows.
|From each app screen, press the device's Home key or swipe up in gesture navigation, then re-launch the app from the All Apps screen.
|From each app screen, switch to another running app, and then return to the app under test using the Recents app switcher.
|From each app screen (and dialogs), press the Back button or use the back swipe gesture.
|From each app screen, rotate the device between landscape and portrait orientation at least three times.
|Switch to another app to send the test app into the background. Go to Settings and check whether the test app has any services running while in the background. In Android 4.0 and higher, go to the Apps screen and find the app in the "Running" tab.
|Press the power button to put the device to sleep, then press the power button again to wake the screen.
|Set up a screen lock on the device. Press the power button to put the device to sleep (which locks the device). Then, press the power button again to wake the screen and unlock the device.
|Trigger and observe in the notifications drawer all types of notifications that the app can display. Expand notifications where applicable (Android 4.1 and higher), and tap on all available actions.
|Review Support for other use cases in Doze and App Standby.
|Install on SD Card
|Repeat Core Suite with the app installed to a device’s SD card (if the app supports this installation method).
To move the app to SD card, you can use Settings > App Info > Move to SD Card.
|Performance and Stability
|Review the Android manifest file and build configuration to ensure that the application is built against the latest available SDK (
build.gradle file for any outdated dependencies.
|Use the Android Studio lint tool to detect non-SDK interface usage. Other alternative testing methods also exist.
|Repeat Core Suite with StrictMode profiling enabled.
Pay close attention to garbage collection and its impact on the user experience.
|Repeat Core Suite across Doze and App Standby cycles.
Pay close attention to alarms, timers, notifications, syncs, and so on. See Testing with Doze and App Standby for requirements and guidelines.
|Review all data stored in external storage.
|Review how the data that’s loaded from external storage is handled and processed.
|Review all content providers defined in the Android manifest file. Make sure each provider has an appropriate
|Review all permissions that your app requires, in the manifest file, at runtime, and in the app settings screen (Settings > App Info) on the device.
|Review all application components defined in the Android manifest file for the appropriate export state. The exported property must be set explicitly for all components.
|Review the app's Network Security configuration, ensuring that no lint checks on the configuration fail.
|In each WebView, attempt to navigate to sites and content that aren’t loaded directly by your app.
|Declare a Network Security Configuration that disables cleartext traffic, then test the app.
|Run the application and exercise all core functionality, while observing the device log. No private user information should be logged.
|Sign into the Google Play Developer Console to review your developer profile, app description, screenshots, feature graphic, content rating and user feedback.
|Download your feature graphic and screenshots, and scale them down to match the display sizes on the devices and form factors that you are targeting.
|Review all graphical assets, media, text, code libraries, and other content that’s packaged in the app or expansion file download.
Testing with StrictMode
For performance testing, we recommend enabling
StrictMode in your
app and using it to catch operations that could affect performance, network accesses, file
reads/writes, and so on. Look for potentially problematic operations both on the main thread and on
Make sure to enable visual notification of policy violations for the