# android-app-bundle Published articles for android-app-bundle. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Keeping Up with Android App Size Growth DevFeed: [Keeping Up with Android App Size Growth]() Original publisher: [Read original article]() Author: Justin Wong Published: 2023-06-27T06:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [LineageOS](), [APK](), [ci](), [Mobile](), [Development]() Tags: [android](), [android-app-bundle](), [android-studio](), [apk](), [app-size](), [build](), [ci](), [development](), [engineering](), [google-play](), [libraries](), [mobile-apps](), [pipeline](), [script]() ### AI overview Square describes how it manages Android app size growth across a monorepo by applying size-reduction techniques, tracking changes in continuous integration, and improving team accountability. The post also covers automation and tools for identifying savings and comparing APK versions. ### Source excerpt Tracking app size changes in CI and ensuring team accountability ## Reducing Android app size in practice at LinkedIn DevFeed: [Reducing Android app size in practice at LinkedIn]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-11-23T16:53:49Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [Android](), [App](), [Google Play](), [APK](), [modules](), [Azure]() Tags: [android](), [android-app-bundle](), [android-app-development](), [apk](), [app-size](), [azure](), [google-play](), [jetpack-compose](), [modules](), [optimization](), [sdk]() ### AI overview This article explains how LinkedIn reduced Android app download size in practice. It distinguishes download, install, and storage sizes, then discusses Android App Bundle optimizations and Play Feature Delivery, including their use with the Azure Communication Services SDK for Native Video Meeting. ### Source excerpt Photo: Daniel Romero from Unsplash App size is a key metric impacting user acquisition and retention: If the app is too large to download, users may skip installation or cancel the installation during downloading; if the app takes too much storage space after use, users may choose to uninstall. There are also different measurements of Android app sizes: Download size: The compressed size of the release downloaded by users at install time. Install size: The approximate size of the recent release on the user's device after installation, but before the app is opened for the first time. Space used shown in Storage Settings: Sizes of files under cache directory and other directories under /data/data/com.app.package.name This post mainly focuses on the download size. This is displayed directly in the Google Play console for developers, and also displayed in the about this app section in Play Store. The official documentation on Android Developers already covers many different ways to optimize the app size. However, in this blog post, we would like to emphasize some of the less known yet powerful techniques to reduce app size. These techniques helped LinkedIn to minimize its app size in recent years. Play Feature Deliverya.k.a Dynamic Features, Dynamic Modules, or On-Demand modules Android App Bundle, as a publishing format in Google Play, was recently escalated to the requirement for publishing new applications in August 2021. The app bundle is used to generate multiple optimized APKs. Then the user will only download the specific APK set optimized for their device. The download size savings come from: ABI libraries that do not match the device's processor architecture Resource files that do not match screen density Language resources that do not match the user's device language Application size savings from Android App Bundle (Google I/O 2018) -- https://youtu.be/flU42CTF3MQ Migrating to an Android App Bundle should be a streamlined process. At least this was the case for ## Android App Bundle Support DevFeed: [Android App Bundle Support]() Original publisher: [Read original article]() Author: Shai Almog Published: 2021-05-08T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Google Play](), [Android](), [Google](), [APK]() Tags: [android](), [android-app-bundle](), [apk](), [google](), [google-play]() ### AI overview Codename One has added Android App Bundle support. The build produces both an APK and an app bundle for submission to Google Play, where the app bundle is becoming the required format. ### Source excerpt We have added Android App Bundle support which will become the required format for submitting apps to Google Play. ## Aircall Journey to Android App Bundle DevFeed: [Aircall Journey to Android App Bundle]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2021-02-18T15:12:51Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Android](), [APK](), [Gradle](), [Optimization](), [CircleCI](), [feature flags](), [ci]() Tags: [android](), [android-app-bundle](), [androiddev](), [apk](), [ci](), [circleci](), [continuous-integration](), [feature-flags](), [gradle](), [optimization](), [play-store]() ### AI overview Aircall describes migrating its Android app from APK distribution to Android App Bundle to deliver optimized APKs. The article covers APK size reduction, language, density, and ABI splits, Gradle configuration, and planned Play Feature Delivery, with CircleCI and fastlane mentioned for release automation. ### Source excerpt A couple months, we decided to use Android App Bundle (AAB) to distribute Aircall's Android app in Play Store. After analyzing the Aircall Android application package (APK), we found we could deliver optimized APKs to our users -- an overall size reduction of 60%! In this article, we are going to expose our journey to Android App Bundle from our own motivations to the development within the application and the CI with CircleCI and fastlane to release on the Play Store. Why move to App Bundle? Moving to App Bundle had many advantages. The first and main reason was the APK size optimization, to deliver only what the user needs. After looking at our application file, we found that we embedded all native libraries (.so files) of all supported architectures! We could have used the abi split in our main build.gradle but we would have managed 4 APKs with different version code. We also saw we could reduce the resource assets to match the density of the device where the app is installed. Here is what the Aircall universal APK looks like on the inside: APK analysis with Android Studio Optimizing size was not the only advantage we saw. Migrating to AAB will allow us (a little bit) to save the planet! Indeed, with all the MB saved from the downloads and updates, we are using less storage space and consuming fewer energy resources. You can see our MAD Score below. If it hits 1 million downloads we could save 22 TB of data -- really a huge impact. MAD Score data from the Aircall project We were also excited by our future ability to enable Play Feature Delivery to push features to specific users. Since we are already using feature flags inside our applications, this would let us develop features on-the-go for our users. Gradle configuration Moving to AAB was a very smooth process and did not require a lot of configuration code. To replicate this move, on your build.gradle of your application, add the following block to build an AAB file. You will be able to add the language, densit