android-ux

Applies Material Design 3 UX principles to design and audit Android Compose screens.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/chmonya-inc/dnd-manager --skill android-ux-chmonya-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-ux
Source: https://github.com/chmonya-inc/dnd-manager/tree/main/.agents/skills/android-ux
Command: npx skills add https://github.com/chmonya-inc/dnd-manager --skill android-ux-chmonya-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Android screens often violate platform conventions — undersized touch targets, missing content descriptions, hardcoded colors, or broken back navigation — leading to poor usability and failed accessibility reviews. This Skill provides concrete Material Design 3 rules and a structured audit so screens feel native, accessible, and responsive. ## Core Features & Use Cases - UX Guidelines: Covers touch targets (48dp minimum), press feedback, gestures, haptics, navigation patterns, safe area insets, spacing grids, adaptive layouts, foldable postures, forms, and animation timing with Compose code examples. - Accessibility Rules: Enforces content descriptions, semantics, heading markers, WCAG AA contrast ratios, M3 contrast levels, and dynamic type support. - M3 Compliance Audit: Scores a screen across 10 categories (color tokens, typography, shape, elevation, components, layout, navigation, motion, accessibility, theming) with a Pass/Partial/Fail summary template. - Use Case: Before shipping a new settings screen, run the M3 compliance audit to catch hardcoded colors, missing content descriptions, and a missing tablet breakpoint, then fix each Partial/Fail item. ## Quick Start Review this Compose screen for Material Design 3 compliance and list all accessibility and touch target violations.

Frequently Asked Questions about android-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make Android touch targets accessible in Jetpack Compose?▼

Touch targets must be at least 48x48dp with 8dp spacing between adjacent targets. Use IconButton, which enforces 48dp by default, or apply Modifier.minimumInteractiveComponentSize() to expand the tap area of smaller visual elements.

How to audit a Compose screen for Material Design 3 compliance?▼

Score the screen across 10 categories: color tokens, typography, shape, elevation, components, layout, navigation, motion, accessibility, and theming consistency. Mark each as Pass, Partial, or Fail, then resolve all Partial and Fail items before shipping.

Does Compose support foldable device layouts?▼

Yes, use WindowInfoTracker and FoldingFeature from Jetpack WindowManager to detect postures like tabletop and book mode. Never place interactive content across the hinge, and switch layouts based on fold orientation and state.

What contrast ratio is required for Android accessibility?▼

WCAG AA requires 4.5:1 contrast for body text and 3:1 for large text (18sp+ or 14sp+ bold) and UI components. Test ratios in both light and dark themes independently, and consider M3 contrast levels for user-controlled adjustment.

Why should I avoid hardcoded padding for system bars in Compose?▼

Hardcoded padding breaks across devices with different status bar heights, cutouts, and gesture navigation. Always consume the innerPadding provided by Scaffold or use WindowInsets APIs so content respects safe areas automatically.

How do I respect reduced motion settings in Compose animations?▼

Compose has no built-in reduced motion flag, so create a CompositionLocal that reads Settings.Global.ANIMATOR_DURATION_SCALE. When the user has disabled animations, skip or simplify transitions such as replacing slide animations with EnterTransition.None.