android-native-dev

To configure Gradle build variants for Jetpack Compose, use the Compose BOM for dependency versions and define your flavors and buildTypes to generate predictable assemble commands. This ensures variant setup aligns with AndroidX and Material 3 standards for reliable builds.

Gradle build failures during Android compilation often stem from AAPT resource conflicts or incorrect dependency versions. You can resolve these build errors by checking the gradle.properties file for AndroidX/Jetifier settings and running diagnostic steps to identify specific resource or dependency conflicts.

Best practices for Compose state and coroutines involve enforcing null-safety and exception-handling discipline while correctly routing tasks between Main and IO/Default threads. Following these guardrails prevents common crashes and ensures stable UI rendering in Kotlin.

To meet Material 3 accessibility requirements in Android, apply theming rules and ensure touch target sizing meets minimum dimensions. You must also follow contrast guidance and resource naming rules, including avoiding reserved names, to achieve full compliance.

Yes, you can use this skill to recover an existing partial Android Studio project. It assesses your project scenario and provides a required-file checklist to standardize Gradle setup and dependencies before you implement any business logic.

For a native Android Kotlin app, you should establish test layering using unit tests, Robolectric, Espresso, and Compose tests. This quality workflow helps catch errors early and verifies that your Gradle build variants function correctly across different configurations.