Flutter Networking

Keep transport concerns at the service boundary and expose domain-meaningful results to the rest of the app.

Select the mode

• Handle ordinary HTTP request-response work with the rules below.
• For GraphQL operations, generated models, normalized caches, optimistic writes, or subscriptions, read GraphQL clients.
• For WebSocket, SSE, Socket.IO, connection recovery, or live event delivery, read Realtime transports.
• For REST or HTTP response debugging, undocumented fields, decoding drift, or comparing Swagger/OpenAPI with deployed behavior, read HTTP response evidence.
• Read both references for GraphQL subscriptions. Route stream races or subscription leaks to dart-concurrency, durable offline queues to flutter-persistence, and terminated-app alerts to flutter-notifications.
• Audio/video capture, media tracks, playback, and call sessions belong to flutter-media; keep text/data transport and upload behavior here.

Inspect

Read current client, generated API code, interceptors, model generation, authentication, environment configuration, and tests. Preserve http, Dio, generated clients, or another established choice when it meets the requirement.

Rules