Android Native Feel Checklist for AI-Built Screens

Direct answer

An Android native feel checklist verifies that generated screens behave like Android screens rather than generic responsive web pages. It should cover 48dp targets, Material controls, back behavior, status/navigation bars, keyboard handling, TalkBack labels, and offline/error states.

Where it fits

• A Gemini or Codex-built Android prototype needs a native-polish pass before user testing.
• A design system owner wants to keep generated screens aligned with Material patterns.
• A QA lead needs a checklist that a non-designer can apply consistently.

How to run the review

1. Check 48dp tap targets, label proximity, and spacing rhythm.
2. Verify system back, modal dismissal, swipe rows, keyboard avoidance, and bottom navigation safe areas.
3. Review Material switches, inputs, sheets, snackbars, and navigation patterns.
4. Run TalkBack label, order, contrast, and dynamic font checks.

Common risks

• Bespoke controls can look modern but fail Android semantics.
• Ignoring the system back gesture causes navigation loops and review complaints.
• Bottom controls can become unusable around gesture navigation bars and keyboards.

How NativeFeel QA helps

NativeFeel QA packages Android native-feel checks into scorecards and exact fix prompts for AI-generated screen repairs.