A mobile developer agent implements features and fixes for iOS, Android, or cross-platform mobile applications. It handles the platform-specific constraints that desktop and server code does not face: offline state, background limits, push notification permissions, and app store compliance requirements.
Mobile development is especially sensitive to the target platform and framework. A React Native agent writes very different code than a SwiftUI agent. The role-specific prompt must specify the platform, the navigation framework, the state management approach, and any platform-specific compliance rules your app follows.
What this agent owns
- Implement screens, navigation flows, and interactions from design specifications
- Handle offline state, network errors, and background sync appropriately for the platform
- Write unit and UI tests using the project's mobile testing framework
- Manage push notification registration, permissions, and payload handling
- Keep platform SDK versions and third-party dependencies current and compatible
Recommended model: Claude Sonnet
Mobile UI implementation and platform integration are well-scoped tasks where Sonnet produces correct, idiomatic code efficiently.
Example tasks
- Build a settings screen with grouped form sections and persistence
- Implement offline caching for a feed view using local storage
- Add push notification deep-link routing to an existing app
- Fix a memory leak in a view that is not releasing observers on dealloc
# create an agent from this template, then start it
$ fleet agent create --name mobile-developer--vendor claude-code --template <template-name>
$ fleet agent start mobile-developer
Find the exact template name with fleet template list.
