Vivek
10/03/2026, 8:37 AMandroid/app product.
Why does an android/app product still use Gradle for compilation/building? If Gradle is still required underneath, what are the main advantages of using Kotlin Toolchain over using Gradle directly?
Also, is it technically possible (or planned) to build an android/app product without Gradle at all, with Kotlin Toolchain handling the complete build process?
I'm asking because one of the things that interests me about Kotlin Toolchain is the possibility of a lightweight, fast build system without the overhead of a Gradle daemon. I'd love to understand what the intended architecture and long-term direction are here.joffrey
10/03/2026, 9:23 AMandroid.jar used in unit tests
• resource processing to produce the R class before we can compile Kotlin code on our end
• APK / AAB packing (using the classes compiled on our end, and dependencies we resolved)
◦ This includes artifacts transformation, D8 dexing, R8 minification, manifest merging, and signing
For the mockable JAR, we already asked Google if they could extract the generator in a way we can reuse more easily, so we don't have to delegate that part to Gradle.
For R, APK, and AAB, it's a bit more tricky, but the end game is indeed to replace this with delegation to Android tooling instead of Gradle. That may require some help from Google.joffrey
10/03/2026, 9:26 AM