Mobile App Developer

What it does

Mobile App Developer is a Cursor agent playbook named mobile-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The mobile-engineer agent creates cross-platform mobile experiences for iOS and Android. It handles Expo setup, gesture navigation, biometric authentication, offline local SQLite storage, and push notifications.

Builds React Native and Flutter mobile applications with native device APIs. Mobile app engineer for Cursor specializing in React Native, Expo, Flutter, mobile navigation, push notifications, and offline caching.

Why it exists

A pile of agent files is not a team. mobile-engineer exists so one job, mobile app developer, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: React Native & Mobile App Development; Design Systems, Tokens & Vanilla CSS Architecture; Strict TypeScript Standards & Type Safety. Commands that adopt this role: /mobile-screen: React Native Mobile Screen Builder; /build-page: UI Page & Responsive Component Builder; /ship: End-to-End Feature Pipeline Shipper.

When to use it

• Building mobile companion apps for your web SaaS
• Implementing biometric login and push notification services
• Optimizing mobile UI performance and touch gesture responsiveness

When not to use it

• Do not ask mobile-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/mobile-engineer is on disk.
2. Run /mobile-screen: React Native Mobile Screen Builder, or start a chat and tell Cursor to adopt the mobile-engineer role.
3. The agent should read: React Native & Mobile App Development; Design Systems, Tokens & Vanilla CSS Architecture; Strict TypeScript Standards & Type Safety.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are mobile-engineer. Building mobile companion apps for your web SaaS. Read mobile-react-native before you edit."

Or let the pipeline invoke it: /mobile-screen: React Native Mobile Screen Builder.

Capabilities you should actually see: React Native & Expo cross-platform app development

Example output

• mobile-engineer should leave files or a written verdict, not a vibe check. React Native & Expo cross-platform app development Mobile navigation (Expo Router / React Navigation)
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• React Native & Expo cross-platform app development
• Mobile navigation (Expo Router / React Navigation)
• Native device hardware integration (camera, biometrics, GPS)
• Offline data synchronization using WatermelonDB or SQLite
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using mobile-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.