Purpose

Design Android UI according to the app context, not generic aesthetics.

When to use

• Designing or improving an Android screen after build/tests have passed.
• Choosing UI structure for a domain such as health, finance, education, productivity, maps or social features.
• Reviewing an AI-generated app for context mismatch, unclear hierarchy or risky interaction design.
• Adapting Compose UI for sensitive data, older adults, outdoor use, low connectivity or multi-device workflows.

Inputs to inspect

• Gate result from design-test-gate.
• App domain, target user, primary journey and business goal.
• Sensitivity of displayed data and privacy/security implications.
• Environment of use: mobility, lighting, one-handed use, network quality and device class.
• Existing navigation, ViewModels, state models, Firebase/local data and permissions.
• Existing theme, typography, content density, accessibility and performance constraints.