Android App Bundles versus Universal APKs

WHAT THIS TESTS Whether you understand that the artifact you upload to Play differs from what installs on a user's device, and why Google made bundles mandatory.

A GOOD ANSWER COVERS An Android App Bundle is a packaging and publishing format that contains all compiled code and resources but is not itself installable on a device. You upload it to Play, and through dynamic delivery Play generates a set of split APKs optimized for each device configuration, slicing by CPU ABI, screen density, and language. A device then downloads only the splits it needs, so a user on arm64 with one locale never downloads x86 native libraries or other languages' strings. This shrinks download and install size meaningfully for apps with multiple native architectures, which is common in React Native because of bundled native modules. Play App Signing holds the final signing key and signs the generated APKs.

COMMON WRONG ANSWERS Saying you can install an .aab directly with adb; you cannot without first extracting APKs via bundletool. Claiming the bundle is just a compressed universal APK. Forgetting that Play, not your machine, performs the final signing under Play App Signing.

LIKELY FOLLOW-UPS How to test an AAB locally with bundletool. The difference between the upload key and the app signing key. Why universal APKs are larger because they include every ABI.

ONE CONCRETE EXAMPLE A React Native app bundles native libraries for armeabi-v7a, arm64-v8a, and x86. A universal APK includes all three, bloating the download. Uploaded as an AAB, Play delivers an arm64 device only the arm64 split, cutting tens of megabytes from the install.