The End of the Fat APK: Google’s Move Towards Bundles Changes Sideloading Landscape
Google’s transition to Android App Bundles (AABs) in 2018 aimed to streamline app delivery by allowing the Google Play Store to download only necessary components for each device. While this move was beneficial for Play Store users, it has recently brought about a change for those who prefer sideloading apps. Recent claims suggest that Google has stopped generating "fat" APKs for many apps, forcing those who wish to sideload to use bundles instead. This change introduces a new hurdle, requiring additional tools and potentially complicating the sideloading process.
Sideloading Android Apps: A New Era of Bundles
Sideloading, traditionally a simple process involving downloading and installing an APK file, might become more complex with Google’s shift towards bundles. APK bundles, consisting of code and resources packaged as a single file, offer advantages in terms of efficient delivery and minimized storage space. However, this transition means users can no longer simply download and install large APK files from sources like official websites or third-party platforms. Instead, they need to download bundles, which require additional steps for installation.
Artem Russakovskii, founder of APKMirror, reported on X that Google has stopped generating "fat" APKs for a significant number of apps, making bundles the only available format. This change means users who wish to sideload these apps must rely on tools like Split APKs Installer (SAI). SAI is a third-party tool specifically designed to install split APKs, enabling users to extract and install the required components from bundles.
Why This Matters: A Deeper Dive into Bundles and Their Impact
Google’s introduction of AABs aimed to address the inefficiencies of traditional fat APKs, which often contained unnecessary files for different devices. A fat APK, designed to cater to a wide range of screen sizes, CPU architectures, and other device specifications, resulted in unused content occupying valuable storage space on devices. AABs, on the other hand, allow the Play Store to download only the essential components required for each specific device, thereby optimizing storage utilization and improving download speeds.
This move towards bundles, while beneficial for Play Store users, poses challenges for those who prefer sideloading. The additional steps involved in installing bundles, requiring users to download and utilize third-party tools, significantly complicate the process. While alternative solutions like extracting and combining individual APKs from bundles might exist, they are not as straightforward as the traditional approach of downloading and installing a single fat APK file.
Implications for Developers and Users
This change has implications for both developers and users. Developers will need to adapt to the bundle format, potentially requiring adjustments to their development workflows and building processes. They must ensure their apps are compatible with the new system and consider the potential challenges associated with AABs.
For users, the shift to bundles significantly impacts the way they sideload apps. The complexities involved in installing bundles necessitate familiarization with tools like SAI, potentially hindering the convenience and accessibility of sideloading. This transition might discourage some users from opting for sideloading, potentially relying solely on the Play Store for app installations.
The Future of Sideloading: A Balancing Act
Google’s decision to discontinue fat APKs for many apps reflects its commitment to promoting efficiency and optimizing app delivery through bundling. This move is likely driven by a desire to enhance user experience by reducing app installation sizes and download times. However, this transition raises concerns about the accessibility and convenience of sideloading, potentially discouraging users from opting for this method.
The future of sideloading might involve a balancing act between Google’s push towards bundles and the preference of users for direct installations. While bundles offer distinct advantages in terms of efficiency and storage optimization, they introduce a barrier to entry for those who prefer sideloading. Whether Google will address these concerns and offer alternative solutions for sideloaders remains to be seen. Ultimately, the success of this transition hinges on finding a compromise that balances the benefits of bundles with the needs of users who rely on sideloading.
