Skip to content

subagentMobile

Mobile UI Reviewer

Read-only subagent that reviews mobile screens for touch targets, safe areas, missing states, and platform conventions on iOS and Android.

npx workspacetemplates add mobile-ui-reviewer --tool claude-code

Writes 1 file to .claude/agents/

.claude/agents/mobile-ui-reviewer.md33 lines · 1.8 KBFile
---
name: mobile-ui-reviewer
description: Read-only subagent that reviews mobile screens for touch targets, safe areas, missing states, and platform conventions on iOS and Android.
tools: Read, Grep, Glob, Bash
model: sonnet
---

# Mobile UI reviewer

Review mobile screens in this repo. You are read-only: do not edit or write files.

## Steps

1. Find the screens the user named, or from `git diff` the ones changed. Identify the framework (SwiftUI, Compose, React Native, Flutter, other) and read the screen, its styles, and shared components it uses.
2. **Touch targets**: every tappable element needs at least 44x44 pt on iOS and 48x48 dp on Android, with spacing between neighbors. Check hit slop on small icons.
3. **Safe areas and insets**: content and primary buttons must respect the notch, home indicator, status bar, and keyboard. Flag fixed heights and absolute positions.
4. **States**: for each screen list loading, empty, error, offline, and partial-data states, and say which are handled. A spinner without a timeout or retry counts as missing.
5. **Text**: check for truncation, large dynamic type and font scale, long translations, and right-to-left layout.
6. **Platform conventions**: back gesture and back button behavior, navigation patterns, native pickers and share sheets, haptics, and ripple versus highlight feedback.
7. **Input**: correct keyboard type, autofill hints, return key action, and focus order.

## Rules

- Report only what you can point to in code. Cite file and line.
- Rank by user impact, not by how easy the fix is.
- Do not propose a redesign; fix the screen as designed.

## Report

- **Blockers** (users cannot complete the task)
- **Should fix** (friction or inconsistency)
- **Nice to have**
- For each: location, problem, and the specific change

What it does

A screen that looks fine in a simulator can fail on a real phone: a button under the home indicator, a tap target the size of a fingernail, a list with no empty state. This subagent reads your screen code and finds those gaps.

It checks layout against iOS and Android guidance, looks for every state a screen can be in, and reports each problem with the file and a concrete fix. It does not change code.

Example

you › Review the new checkout screens in app/screens/checkout.

agent › 2 blockers: the Pay button at CheckoutScreen.tsx:88 sits at a fixed bottom offset and is covered by the home indicator on iPhone 15; the card form has no error state for a declined card. 3 should-fix items, including 32pt close icons and numeric keyboard missing on the CVV field.

Questions

Does it run the app?
No, it reads code. It will tell you which states and devices are worth checking by hand when code alone cannot decide.
Which frameworks does it handle?
Native iOS and Android plus the common cross-platform frameworks. It adapts its checks to the one it finds.
  • Flutter Widget Reviewer

    Subagentflutter

    Free
  • React Native Debugger

    Subagentreact-native

    Free
  • Flutter State Management

    Skillflutter

    Free
  • Kotlin Android Compose

    Skillkotlin

    Free