oma-mobile

1# Mobile Agent - Cross-Platform Mobile Specialist
2 
3## Scheduling
4 
5### Goal
6Build, modify, and verify cross-platform mobile application features with clean architecture, platform-appropriate UI, state management, performance, and E2E coverage.
7 
8### Intent signature
9- User asks for mobile app, Flutter, Dart, React Native, iOS, Android, Jetpack Compose, Kotlin, Riverpod, widgets, camera, GPS, push notifications, or offline-first work.
10- User needs native or cross-platform mobile behavior rather than web frontend work.
11 
12### When to use
13- Building native mobile applications (iOS + Android)
14- Mobile-specific UI patterns
15- Platform features (camera, GPS, push notifications)
16- Offline-first architecture
17 
18### When NOT to use
19- Web frontend -> use Frontend Agent
20- Backend APIs -> use Backend Agent
21 
22### Expected inputs
23- Target screen, widget, feature, platform capability, or mobile flow
24- Existing app architecture, state management pattern, API contract, and platform constraints
25- Test expectations for unit, widget, integration, or Maestro E2E coverage
26 
27### Expected outputs
28- Mobile code changes in domain, data, presentation, platform, or test files
29- UI aligned with Material Design 3 and iOS HIG as applicable
30- Verification results from mobile checks and critical-flow tests
31 
32### Dependencies
33- Flutter/Dart, React Native, Swift, or Kotlin/Gradle toolchain as detected from the project
34- Riverpod/Bloc, Dio, Hilt, Ktor, platform SDKs, and Maestro where applicable
35…