Why does my download android size

Looking at the app manager on the device however shows the following stats:. EDIT: Researching this further, this is a common feature across many applications on my devices. Google Play reports one size and the device reports something generally in the magnitude 2 times greater. So good to know its probably not something I'm doing, but still curious what the reasoning here is as its frustrating to be accused by users of 'doctoring' the install size to appear smaller!

Which contains your code, resources etc compiled as binaries. Your dex is generally the same size of your apk, unless you have resources not compiled in assets. Well, we all know that. Perhaps for reinstalling in case of errors or for some other reasons.

That's why the amount of memory of our apps is the double in system. It's the sum of the size of the original apk and the installed dex. It is like every other software application which will be compressed initially and made as a single file to install and upon installing, it will extract all the files code, assets i.

This is why your app will be more memory after getting installed in a phone. In order to prevent this, make your app a server side and ask compulsory permission for Internet so that you can send the data without consuming more memory for the app. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 8 years, 10 months ago. Active 3 years, 5 months ago. Viewed 12k times. Looking at the app manager on the device however shows the following stats: Total: 6.

What is causing the discrepancy in stats? Improve this question. Chris Knight. Chris Knight Chris Knight Once I opened the system folder and saw a dex file near each apk file. Maybe it is somehow related. 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. App links.

Dependency injection. Core topics. App compatibility. Interact with other apps. Package visibility. Intents and intent filters. User interface. Add motion to your layout with MotionLayout. MotionLayout XML reference.

Improving layout performance. Custom view components. Look and feel. Splash screens. Add the app bar. Control the system UI visibility. Supporting swipe-to-refresh. Pop-up messages overview. Adding search functionality. Creating backward-compatible UIs. Home channels for mobile apps. App widgets. Media app architecture.

Building an audio app. Building a video app. The Google Assistant. Routing between devices. Background tasks. Manage device awake state. Save to shared storage. Save data in a local database. Sharing simple data. Sharing files. Sharing files with NFC. Printing files. Content providers. Autofill framework. Contacts provider. Data backup. Remember and authenticate users.

User location. Using touch gestures. Handling keyboard input. Supporting game controllers. Input method editors. Performing network operations. Transmit network data using Volley. Perform network operations using Cronet. Transferring data without draining the battery. Reduce network battery drain. Transfer data using Sync Adapters.

Bluetooth Low Energy. Wi-Fi infrastructure. Discover and connect. Runtime API reference. Web-based content. Android App Bundles. Google Play. Play Asset Delivery. Play Feature Delivery. In-app reviews. In-app updates. Google Play Instant. Get started with instant apps. Get started with instant games. Integrate with Firebase. Play Install Referrer.

Play Install Referrer Library. Application Licensing.