Integrate Mobile API
Use this skill for integrating backend APIs into Flutter applications.
Workflow
- •Confirm API scope and constraints:
- •protocol (
RESTorGraphQL) - •authentication model (JWT, OAuth, API key, session)
- •required endpoints/operations
- •protocol (
- •Define architecture boundaries:
- •data layer for client/datasource
- •domain layer for repository contracts and use cases
- •presentation layer for state updates
- •Implement API client with safe defaults:
- •timeouts
- •retry/backoff policy where appropriate
- •request/response logging with redaction
- •Add auth handling:
- •token attach/refresh strategy
- •unauthorized flow (
401/403) and sign-out fallback
- •Add DTO mapping and error normalization:
- •map API payloads to domain entities
- •map transport/server failures to typed domain failures
- •Add tests:
- •unit tests for mapping and repository behavior
- •integration tests for happy/error paths (mock server/client)
- •Validate with analysis and impacted tests.
Guardrails
- •Do not expose secrets/tokens in logs or source files.
- •Keep API client concerns in data layer; avoid direct networking in widgets.
- •Do not claim API integration is complete without naming changed files and validation evidence.
- •In simulation/planning mode, use
planned/not executedwording.
Required output
- •API scope and auth model selected.
- •Files changed by layer (presentation/domain/data).
- •Validation commands and results.
- •Error handling and retry strategy summary.
- •Remaining risks/follow-up tasks.
Required references
- •
../../rules/flutter-development-best-practices.mdc - •
../../rules/dart-effective-dart.mdc - •
../../rules/flutter-test-best-practices.mdc