gradle-expert

Gradle build optimization for Kotlin Multiplatform involves profiling build times, enforcing consistent Kotlin and Compose versions across modules, and applying centralized version catalog governance to reduce configuration conflicts and improve build speeds.

Resolving platform-specific dependency variant conflicts in Gradle requires selecting correct variants like jni-jvm for desktop and jni-android for Android, ensuring modules pull appropriate artifacts for their target architecture.

A Gradle version catalog centralizes dependency governance across multi-module architectures, ensuring consistent library versions and platform-specific dependency handling across Android, desktop, and shared commons modules.

You cannot use a single configuration for both Android and desktop JNI dependencies; you must enforce correct dependency variant usage, separating jni-jvm and jni-android artifacts to match platform targets.

The best way to troubleshoot multi-module Gradle dependency resolution failures is to run the analyze-build-time script to generate a performance report, then verify platform-specific variant selection and version catalog consistency.

Gradle builds fail when switching Compose variants due to inconsistent Kotlin and Compose versions across modules; enforcing a centralized version catalog and correct dependency variant usage resolves these configuration mismatches.