The difference is huge: 11 MB! If we consider that my device’s screen resolution is xxhdpi, difference will be even more when target device’s resolution is lower than xxhdpi. My device needs only four of them, which is a total of 27 MB. Intent intent new Intent(this, Example.class) Bundle bundle new Bundle() (key, value) intent.putExtras(bundle). This results in dramatically reduced download sizes!Īs an example, we’ve recently generated an AAB for a project we have been working on, and there were 95 little APKs in it with a total size of 38 MB. It does the same thing for locale and SDK version, prepares a new APK and makes it available for the user. Then looks at the screen size of the same device and takes the matching resources for that specific screen resolution. If the device has a 32-bit processor, app bundle takes compatible APK from the package. With app bundles, users get only what they need based on the device they are installing the app on, instead of having all possible combinations. This is where the new app bundles come in! To be able to support all of these combinations, we used to include everything in the same package and deliver that to all users.
Sreen resolutions (hdpi, xhdpi, xxhdpi…).aab file is generated by the feature, which we are supposed to upload to the Google Play Store. Processor types (arm based armeabi-v7a, arm64-v8a or intel based x86, x86_64…) Google has released the Android App Bundle feature.You might think this has minimal impact, but there are lots of configurations: We can reduce the amount of unnecessary data to an extent with proguard but still we couldn’t generate device configuration specific APKs. Apps binaries that we deliver to the Play Store contain tons of libraries and resources.
0 kommentar(er)
