Split APKs and Android App Bundles explained
Why some Android apps ship as several files instead of one -- what a base APK, a split config APK, and an .aab actually are, and why installing them in the wrong way causes a crash or an install failure.
1Base APK vs. split config APKs
A base APK contains the app's core code and default resources. Split config APKs add device-specific pieces on top -- one per CPU architecture (arm64-v8a, armeabi-v7a, x86_64), one per screen density, and one per language. The Play Store installs only the splits that match YOUR specific device, keeping the download small.
2Why a single split APK alone won't install
A split config APK has no launchable app on its own -- it's meaningless without the matching base APK. This is exactly why XAPK/APKM archive formats exist: they bundle the base APK together with the right splits for a given device into one file a sideload installer can process as a set.
3What .aab (Android App Bundle) is
.aab is the format developers UPLOAD to the Play Store, not something installed directly on a device -- the Play Store itself generates the actual split APKs a device downloads from it. A downloaded .aab file cannot be installed by tapping it; it needs to be converted to a device-installable APK set first (e.g. via the bundletool utility), which is a developer-facing step, not something a typical end user does when sideloading.
4Practical takeaway when sideloading
If a download from this site or elsewhere is a single .apk, it installs directly like any normal file. If it's an .xapk/.apkm archive, use a split-APK installer app (see the XAPK guide in this section) rather than trying to extract and install pieces manually.