What does flutter build appbundle --release do to minimize size?

WHAT THIS TESTS: This question probes whether you understand the multi-layer build pipeline in Flutter and can clearly separate Dart-side optimizations from Android-side optimizations. A senior engineer should know that tree-shaking happens in the Dart compiler while R8 is an Android-specific tool, and they should be able to explain how app bundle format adds another layer of size reduction.

A GOOD ANSWER COVERS: Four things in order. First, the Dart frontend performs tree-shaking during AOT compilation. It analyzes the entry point and dependency graph to eliminate unused classes, functions, and libraries from the final kernel snapshot and machine code. This is purely a Dart optimization and happens before the Android build begins. Second, the Flutter tool invokes the Android Gradle build, where R8 operates on the Java and Kotlin bytecode. R8 shrinks code by removing unused classes and methods, obfuscates identifiers to reduce string pool size, and optimizes control flow. Third, the app bundle format enables dynamic delivery. Google Play generates split APKs from the AAB, serving only the native libraries matching the target device ABI, along with language and density splits if configured. Fourth, mention that these are complementary: tree-shaking handles Dart bloat, R8 handles Android bloat, and AAB handles distribution bloat.

COMMON WRONG ANSWERS: Saying that R8 tree-shakes Dart code is the biggest red flag; R8 never sees Dart source or Dart AOT output because the Dart compiler has already finished. Confusing ProGuard with R8 is another mistake; while ProGuard only shrinks and obfuscates, R8 also performs desugaring and is the default in modern Android Gradle Plugin. Some candidates also forget that app bundles are what enable per-ABI splitting and incorrectly attribute ABI filtering to the build command itself. Finally, omitting tree-shaking entirely or describing it as a manual step rather than an automatic compiler optimization signals weak Dart knowledge.

LIKELY FOLLOW-UPS: An interviewer might ask how to verify the size impact of each stage, such as using app bundle explorer in Play Console or analyzing the APK with Android Studio. They might ask how to keep code from being tree-shaken, leading to a discussion of keep annotations in Dart or ProGuard rules for Android. They could also ask about iOS equivalents, prompting a comparison with LLVM bitcode stripping and App Thinning.

ONE CONCRETE EXAMPLE: If your Flutter app imports the entire material icons font but only uses 20 icons, tree-shaking removes the unused icon glyphs from the Dart compilation output. On the Android side, if you include a legacy analytics SDK in your Gradle dependencies but never initialize it, R8 detects the unreachable Java classes and strips them from the DEX files. When you upload the resulting app bundle, a user with an arm64-v8a device receives an APK containing only the arm64 Flutter engine and stripped DEX, cutting the download size by roughly 3 to 5 megabytes compared to a universal APK.