To help you build efficient apps that are optimized for size, you can check the download and install sizes of your app’s releases and find out how your app’s size has changed over time.
App size is one of the biggest factors that can affect your app’s install and uninstall metrics. It’s important to regularly monitor and understand how you can reduce your app’s download and install sizes. Since the two sizes are related, here’s how they’re different from each other:
- App download size: The size of your app that users download on Google Play. When an app has a larger download size, it takes longer to download.
- App size on device: The amount of space required to install your app. Since apps are compressed when they’re downloaded, it can make install sizes larger than download sizes. When an app has a larger install size, more space is required on a user’s device to complete installation. After the app is opened, its size on disk varies depending on app usage.
Note: All sizes are representative calculations based on your latest production release and the
XXXHDPI ARMv8 device configuration or the closest supported device configuration for your app.
After you’ve released your app on a production track, here’s where you can see your app’s download and install sizes:
- Open Play Console and go to the App size page (Android vitals > App size).
- At the top right of the screen, filter page data by App download size or App size on device.
You can find the following data on the App size page:
- App download size/App size on device: Your app’s size on a reference device and its size range across all device configurations.
- App download size/App size on device vs. peers: How your app’s size compares to peers.
- To create a custom peer group of 8-12 apps, click Edit peer group.
- App download size/App size on device over time: How your app’s size has changed and compares to peers over time.
- Near the top-right of the chart, you can select the date range that you want to view and check the checkbox to display your app’s size range across all device configurations.
- Active devices with <1GB free*: The percentage of your app's active users with less than 1GB of device storage space remaining.
- Uninstalls on devices with <1GB free*: The ratio of uninstalls on active devices with less than 1GB of storage space remaining to uninstalls on all active devices.
Note: The Active devices with <1GB free and Uninstalls on devices with <1GB free metrics are calculated based on a 30-day rolling average and are only shown when determined to be applicable to your app.
If you publish apps using the Android App Bundle, you can view a chart that’s organized by bundle version code with a breakdown of how much space different components of your app account for when compared to your app’s total download or install size for your previous five releases.
You can use this breakdown to find out what parts of your app are taking up the most space and identify areas that you can further optimize for space. The breakdown is based on an APK generated from your app bundle for the reference device configuration.
The breakdowns show the following data:
- App download size breakdown:
- Code/DEX: All Java or Kotlin code in your app compiled for execution on Android in DEX format.
- Resources: Resources include the resource table and non-code components of your app in the res/ directory, such as strings or images.
- Assets: Assets are other files that your app uses in the assets/directory, such as sound files or videos.
- Native libraries: The native code in the libs/ directory of your app. This is typically any code that is not Java or Kotlin.
- Other: Other files in your app.
- App size on device breakdown additionally shows:
- Extracted native libraries: When native libraries are compressed in an APK, they must be extracted into local storage to run your app.
- Optimized DEX: DEX code converted to native code by the Android runtime for performance.
Near the center of the page, you can view recommendations to optimize your app's size based on an analysis of your most recent release.
If you publish your app using an APK, you’ll see a suggestion to use an app bundle with an estimate of your potential size savings. If you publish your app using an app bundle, a more thorough analysis is available, and you’ll see a list of suggested optimizations.
Each optimization includes specific guidance on what changes to make and, when it’s possible to calculate an estimate, the potential size savings you’d achieve by implementing the changes. Size estimates are independent estimates and are likely to be different if you implement multiple optimizations at the same time.