In 2018, Google introduced the Android App Bundle (AAB) installation packages, which by 2021 became the default format for applications on the Google Play Store. Developers now need to submit their apps in AAB format for distribution.
The AAB format’s primary benefit is its adaptability. Instead of downloading a complete installation package, Google Play customizes the download based on the device’s screen size, language, CPU architecture, and Android version. This customization significantly reduces the size of the installation package, saving network traffic and space on Android devices.
To allow users to share APK files, Google Play could generate full-size APKs from AAB files, known as fat APKs. These fat APKs enable users to export and share APK files for sideloading and installation.
APKMirrors Announcement: Google’s New Policy
Recently, APKMirrors, a prominent site for APK installation files, announced that Google has ceased generating fat APKs for applications. Now, Google only offers bundled versions, impacting users’ ability to directly download APK files for installation.
Despite this change, the AAB format can still be installed via third-party tools and ADB commands. However, these methods involve more steps, making them less convenient than directly downloading and installing APK files.
Uncertainty Surrounding Google’s Decision
The Android system itself remains unchanged. The reason behind Google’s decision to stop providing fat APKs is unclear. It appears Google aims to reduce the crawling of applications from Google Play and encourage users to download and install apps directly through the Play Store.
For developers who distribute applications beyond Google Play, publishing APK installation packages on their websites remains a viable option. This approach caters to users unable to access Google Play, making it easier for them to install apps directly via APK files.
Related topics: