In a strategic move to streamline app installations and optimize storage, Google has been refining the way Android applications are packaged and delivered. This initiative, which began with the introduction of the Android App Bundle (AAB) at the I/O 2018 conference, has evolved significantly since it became the default format for new applications in 2021.
Transition to Android App Bundles
Developers are now encouraged to create their applications as bundles, which encapsulate various files tailored for different screen sizes, languages, CPU architectures, and Android versions. This innovative approach allows Google Play to download only the necessary components for an app to function optimally on a specific device, thereby conserving valuable storage space. The process is seamless for developers, as Google Play automates the handling of these bundles once they are uploaded.
Previously, while most applications were delivered in this optimized manner, Google Play also had the capability to generate full-size APKs from AAB files. These “fat APKs” were particularly useful for users who shared apps or updates locally or through third-party services like APKMirror. However, recent reports from Artem Russakovskii of APKMirror indicate a significant shift: “Google stopped generating fat APKs for many apps entirely all of a sudden, and only bundles will be available from now on.”
The term “fat APKs” refers to the traditional method of packaging that included all necessary files for various device configurations in a single release. As Google highlighted back in 2018, this approach often led to cumbersome file sizes and unnecessary duplication of content on users’ devices. The transition to AABs aims to alleviate these issues, but it does come with a caveat for those who sideload applications.
Implications for Sideloading
For users who exclusively download apps from the Play Store, this change will have little to no impact. However, for those who extract applications from their devices and upload them to third-party services, the absence of fat APKs presents a new challenge. The installation of bundles now requires additional tools, such as the APKMirror Installer or Split APKs Installer (SAI), or the use of ADB, introducing an extra step in the installation process.
While this may not be a significant hurdle, it does represent a shift in user experience. Notably, users attempting to access Google’s own applications on APKMirror still encounter fat APKs, but this is increasingly rare for newer applications, particularly those from third-party developers.
Despite these changes, Android itself remains unchanged in terms of sideloading capabilities. Developers who distribute their applications outside of the Play Store still have the option to provide fat APKs. Google acknowledges the challenges posed by this transition, particularly regarding the installation of sideloaded apps that may lack essential components.
“Partial installs of sideloaded apps—that is, apps that are not installed using the Google Play Store and are missing one or more required split APKs—fail on all Google-certified devices and devices running Android 10 (API level 29) or higher. When downloading your app through the Google Play Store, Google ensures that all required components of the app are installed.”
This evolving landscape of app distribution reflects Google’s commitment to enhancing user experience while also addressing the complexities of app management in a diverse ecosystem. As developers adapt to these changes, the focus remains on delivering efficient, optimized applications that cater to the needs of users across various devices.
FTC: We use income earning auto affiliate links.
