Mobile app development
Assign mobile app work and the engineer implements it with platform-native UX, safe areas, performant lists and gestures, offline/network behavior, tests, and a review-ready PR.
Saves you ~2 h / run
How it works
- Trigger
- When you start the “Mobile feature delivery” workflow.
- Job
- Implement and verify the assigned mobile change across its target platforms for review.
- Outcome
- A tested implementation and pull request draft.
What it installs
Agents 2
-
Mobile Engineer
Reads the mobile stack, implements platform-appropriate features, verifies mobile states and performance, and drafts a PR.
-
Mobile app development Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Mobile app development quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Mobile feature delivery
Implement and verify the assigned mobile change across its target platforms before human review.
Goals 1
-
Mobile features feel native
Keep mobile work platform-appropriate, performant, tested, and reviewable. Success looks like: Every assigned mobile change respects platform conventions, handles mobile states, passes the documented checks, and reaches review with platform coverage notes.
Skills 3
-
mobile-development
Cross-platform mobile development guidance for React Native, Expo, Flutter, Swift, Kotlin, offline-first sync, performance, testing, and store constraints. Adapted from samhvw8/dot-claude/mobile-development.
-
building-native-ui
Expo native UI guidance for routing, tabs, sheets, safe areas, native components, animations, haptics, and platform conventions. Adapted from expo/skills/building-native-ui.
-
react-native-skills
React Native performance, navigation, native module, Expo, and platform API patterns. Adapted from vercel-labs/agent-skills/react-native-skills.
Requirements
- Connected repository — Needs a connected mobile or cross-platform app repository so the agent can inspect navigation, state, styling, native modules, tests, and build setup.
- Mobile build or simulator context — Needs documented iOS, Android, Expo, or React Native commands, plus any simulator, device, or store constraints the feature must respect.
Setup guide
How to Build Mobile App Features With an Agent
A practical guide to assigning mobile features to an agent while preserving native UX, performance checks, and review-ready delivery.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.