Android app too big to download

Use the arm-eabi-strip tool, provided in the Android NDK, to remove unnecessary debug symbols from native libraries. After that, you can compile your release build. When building the release version of your app, package uncompressed.

Disabling this flag prevents PackageManager from copying. When building your app using Android Gradle plugin 3. Your APK might contain content that users download but never use, like additional language or per-screen-density resources. To ensure a minimal download for your users, you should upload your app to Google Play using Android App Bundles.

If you're not publishing your app to Google Play, you can segment your app into several APKs, differentiated by factors such as screen size or GPU texture support. When a user downloads your app, their device receives the correct APK based on the device's features and settings. This way, devices don't receive assets for features that the devices don't have. Content and code samples on this page are subject to the licenses described in the Content License.

App Basics. Build your first app. App resources. Resource types. App manifest file. Device compatibility. Multiple APK support. Tablets, large screens, and foldables. Build responsive UIs. Build for foldables. Getting started. Handling data. User input. Watch Face Studio. Health services. Creating watch faces. Android TV. Build TV Apps. Build TV playback apps. Help users find content on TV. Recommend TV content. Watch Next. Build TV games. Build TV input services.

TV Accessibility. Android for Cars. Build media apps for cars. Build navigation, parking, and charging apps for cars. Android Things. Supported hardware. Advanced setup. Build apps. Create a Things app. Communicate with wireless devices. Configure devices. Interact with peripherals. Build user-space drivers. Manage devices. Create a build. Push an update. Chrome OS devices. App architecture.

Architecture Components. UI layer libraries. View binding. Data binding library. Lifecycle-aware components. Paging Library. Paging 2. Data layer libraries. How-To Guides. Advanced Concepts. Threading in WorkManager. App entry points. App shortcuts. App navigation. Navigation component. Asked 4 years, 4 months ago. Active 4 years, 4 months ago. Viewed 2k times. Check my gradle config below. And why it is too big? Sp4Rx Sp4Rx 1, 2 2 gold badges 16 16 silver badges 30 30 bronze badges.

You are using many dependencies — IntelliJ Amiya. What libraries are you using? IntelliJAmiya Can I get any analysis which dependency takes how much space. So I can remove that or thing of other solutions — Sp4Rx. I would imagine it is going to be either: " compile 'com. Show 5 more comments. Active Oldest Votes. Your problem is you are using many libraries, The worst of which being: "com. I can confirm that. For example, the sample app provided in the Apk Expansion package calls the following method in the activity's onCreate method to check whether the expansion files already exist on the device:.

In this case, each XAPKFile object holds the version number and file size of a known expansion file and a boolean as to whether it's the main expansion file. See the sample app's SampleDownloaderActivity class for details. The method returns an integer that indicates whether or not the download is required.

Possible values are:. In order to instantiate your IStub by calling CreateStub , you must pass it an implementation of the IDownloaderClient interface and your DownloaderService implementation. The next section about Receiving download progress discusses the IDownloaderClient interface, which you should usually implement in your Activity class so you can update the activity UI when the download state changes. For example, in the previous code sample for onCreate , you can respond to the startDownloadServiceIfRequired result like this:.

After the onCreate method returns, your activity receives a call to onResume , which is where you should then call connect on the IStub , passing it your app's Context. Conversely, you should call disconnect in your activity's onStop callback. Calling connect on the IStub binds your activity to the DownloaderService such that your activity receives callbacks regarding changes to the download state through the IDownloaderClient interface.

To receive updates regarding the download progress and to interact with the DownloaderService , you must implement the Downloader Library's IDownloaderClient interface. Usually, the activity you use to start the download should implement this interface in order to display the download progress and send requests to the service.

With the IDownloaderService object initialized, you can send commands to the downloader service, such as to pause and resume the download requestPauseDownload and requestContinueDownload. To provide a useful message to your users, you can request a corresponding string for each state by calling Helpers. This returns the resource ID for one of the strings bundled with the Downloader Library.

Tip: For examples of these callbacks that update the download progress UI, see the SampleDownloaderActivity in the sample app provided with the Apk Expansion package.

Some public methods for the IDownloaderService interface you might find useful are:. Note: If you do use the Downloader Library as discussed in the previous section, the library performs all interaction with the APKExpansionPolicy so you don't have to use this class directly. The class includes methods to help you get the necessary information about the available expansion files:.

For more information about how to use the APKExpansionPolicy when you're not using the Downloader Library , see the documentation for Adding Licensing to Your App , which explains how to implement a license policy such as this one. Once your APK expansion files are saved on the device, how you read your files depends on the type of file you've used.

Regardless of how you read your files, you should always first check that the external storage is available for reading. There's a chance that the user has the storage mounted to a computer over USB or has actually removed the SD card. Note: When your app starts, you should always check whether the external storage space is available and readable by calling getExternalStorageState.

This returns one of several possible strings that represent the state of the external storage. As described in the overview , your APK expansion files are saved using a specific file name format:. To get the location and names of your expansion files, you should use the getExternalStorageDirectory and getPackageName methods to construct the path to your files.

Here's a method you can use in your app to get an array containing the complete path to both your expansion files:. You can call this method by passing it your app Context and the desired expansion file's version.

There are many ways you could determine the expansion file version number. One simple way is to save the version in a SharedPreferences file when the download begins, by querying the expansion file name with the APKExpansionPolicy class's getExpansionFileName int index method.

You can then get the version code by reading the SharedPreferences file when you want to access the expansion file. For more information about reading from the shared storage, see the Data Storage documentation. This is an optional library that helps you read your expansion files when they're saved as ZIP files. Using this library allows you to easily read resources from your ZIP expansion files as a virtual file system.

If you're using your expansion files to store media files, a ZIP file still allows you to use Android media playback calls that provide offset and length controls such as MediaPlayer. For example, when using the zip tool, you should use the -n option to specify the file suffixes that should not be compressed:.

The above code provides access to any file that exists in either your main expansion file or patch expansion file, by reading from a merged map of all the files from both files. Context and the version number for both the main expansion file and patch expansion file. If you'd rather read from a specific expansion file, you can use the ZipResourceFile constructor with the path to the desired expansion file:. For more information about using this library for your expansion files, look at the sample app's SampleDownloaderActivity class, which includes additional code to verify the downloaded files using CRC.

Beware that if you use this sample as the basis for your own implementation, it requires that you declare the byte size of your expansion files in the xAPKS array. Before publishing your app, there are two things you should test: Reading the expansion files and downloading the files.

Before you upload your app to Google Play, you should test your app's ability to read the files from the shared storage. All you need to do is add the files to the appropriate location on the device shared storage and launch your app:. For example, if your package name is com. Plug in your test device to your computer to mount the shared storage and manually create this directory. For example, regardless of the file type, the main expansion file for the com.

The version code can be whatever value you want. Just remember:. Because your app must sometimes manually download the expansion files when it first opens, it's important that you test this process to be sure your app can successfully query for the URLs, download the files, and save them to the device. To test your app's implementation of the manual download procedure, you can publish it to the internal test track, so it's only available to authorized testers.

If everything works as expected, your app should begin downloading the expansion files as soon as the main activity starts. Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported.

Instead, you must publish it to an internal, closed, or open testing track. Updating Your app One of the great benefits to using expansion files on Google Play is the ability to update your app without re-downloading all of the original assets. Because Google Play allows you to provide two expansion files with each APK, you can use the second file as a "patch" that provides updates and new assets.

Doing so avoids the need to re-download the main expansion file which could be large and expensive for users. The patch expansion file is technically the same as the main expansion file and neither the Android system nor Google Play perform actual patching between your main and patch expansion files.

Your app code must perform any necessary patches itself. Note: Even if you only need to make changes to the patch expansion file, you must still update the APK in order for Google Play to perform an update. If you don't require code changes in the app, you should simply update the versionCode in the manifest. As long as you don't change the main expansion file that's associated with the APK in the Play Console, users who previously installed your app will not download the main expansion file.

Existing users receive only the updated APK and the new patch expansion file retaining the previous main expansion file. Content and code samples on this page are subject to the licenses described in the Content License.

App Basics. Build your first app. App resources. Resource types. App manifest file. Device compatibility. Multiple APK support. Tablets, large screens, and foldables. Build responsive UIs. Build for foldables. Getting started. Handling data. User input. Watch Face Studio.

Health services. The average iOS mobile game is But it is the Newsstand category that is smallest on average. Average newsstand apps come in at This is no surprise since these apps have a focus on content. So they tend to be lightweight. The following chart ranks mobile app categories in order of average file size.

These are figures for iOS mobile apps only. It is also worth noting a correlation between app file size and downloads.

Looking at Android mobile apps, we can see that mobile apps with a large number of downloads tend to be large in file size, too. Of course, this is not unexpected. The most popular mobile apps tend to be feature-rich.