Build Variants & Signing
BUILD & TOOLING › Gradle
Drills build types, flavors, the variant matrix, source sets, and Play App Signing keys.
Build configuration questions probe whether you can ship multiple app versions from one codebase and sign them safely for Google Play. Interviewers test the variant matrix (flavors x build types), how buildConfigField/resValue inject per-variant values, source-set merge priority, and the upload-key vs app-signing-key model under Play App Signing. Expect Gradle DSL reading and 'what gets overridden' reasoning.
What this covers
- Difference between debug and release build types and what each enables (debuggable, minify, signing)
- Product flavors, mandatory flavor dimensions, and how the variant matrix is computed and named
- Injecting per-variant values with buildConfigField (BuildConfig fields) and resValue (generated resources)
- Per-variant source sets and the merge priority order across variant, build type, flavor, and main
- Signing configs: debug keystore vs release keystore and wiring signingConfig per build type
- Play App Signing: upload key vs app signing key, what reset recovers, and key rotation
Study this topic
- Build Variants & Signing explained: the guided lesson
- 13 practice quiz questions
- 9 revision flashcards
- Build Variants & Signing interview questions and answers