mobile-android-design

Wrap your composables in MaterialTheme and use Material 3 components like Card, Button, and NavigationBar, accessing colors via MaterialTheme.colorScheme. The skill provides ready patterns for lists, forms, dialogs, and loading states with proper state hoisting.

Use Navigation Compose 2.7+ with Kotlin serialization, defining routes as @Serializable objects or data classes. Navigate with navController.navigate(Route(args)) and retrieve arguments via backStackEntry.toRoute() for compile-time safety.

Yes, dynamic color (Material You) works on Android 12 and above using dynamicDarkColorScheme or dynamicLightColorScheme with LocalContext. For older versions, fall back to a custom light or dark color scheme.

Use WindowSizeClass to switch between compact, medium, and expanded layouts, pairing bottom navigation on phones with navigation rails or permanent drawers on larger screens. Foldable support uses FoldingFeature state to detect half-opened postures.

Using Column instead of LazyColumn composes every item eagerly, causing jank. Switch to LazyColumn or LazyVerticalGrid with stable item keys, and use remember to avoid unnecessary recomposition of item content.

Interactive elements need contentDescription values and minimum 48dp touch targets. Material 3 tonal palettes help maintain color contrast, and semantic roles like Role.RadioButton should be set on selectable rows.