Purpose

Review a screen like a senior Android UX maintainer: findings first, evidence-based, and safe to act on.

When to use

• Auditing an existing Compose screen before visual changes.
• Reviewing an AI-generated screen for confusing hierarchy or fragile UX.
• Checking forms, dashboards, onboarding, settings, patient/caregiver or sensitive-data flows.
• Deciding which design issues should be fixed now versus deferred.

Inputs to inspect

• Gate result from design-test-gate.
• Screen, route, ViewModel and UI state files.
• Navigation entry and exit points.
• Loading, empty, error, offline and permission states.
• Theme, accessibility semantics, previews and UI tests.
• Performance-sensitive UI such as lazy lists, images or animations.