oma-mobile

Define entities and repository interfaces in the domain layer, implement Dio-based data sources, then create Riverpod providers and screens in the presentation layer. Add unit and widget tests, and use Maestro for critical user flows.

Place the OpenAPI spec at Core/Networking/openapi.yaml with an openapi-generator-config.yaml, attach the OpenAPIGenerator build plugin in Package.swift, and call the generated Client from a service. Never hand-roll URLRequest or JSONDecoder for spec-covered endpoints.

Flutter uses Dart with Riverpod and Drift for offline-first caching, React Native uses TypeScript with TanStack Query and MMKV persistence, and Swift targets iOS 17+ only with SwiftUI and @Observable. Choose based on target platforms and team expertise.

Confirm the class uses the @Observable macro, the deployment target is iOS 17+, and the view holds the view model with @State. Mutations must happen on the main actor, and child views needing mutation require @Bindable.

Cache decoded domain models at the repository layer, never raw HTTP responses. Serve cached data immediately while revalidating in the background, and invalidate affected cache keys on every write operation.

Do not use it for web frontend or backend API work, which belong to separate frontend and backend agents. It targets native and cross-platform mobile features only.