feature/tracking — Realtime Order Tracking (Shared Module)

Realtime order tracking in Flutter uses a Socket.IO client to join order-specific rooms and stream driver_location, order_status_changed, and eta_updated events. A TrackingBloc consumes these streams to update map markers and manage UI states like connecting, active, completed, and error.

Socket.IO room lifecycle for ride-hailing tracking involves joining an order-specific room when the tracking page opens and leaving it upon disposal. This scopes realtime driver location and ETA updates to only the active order, preventing duplicated socket logic and lifecycle bugs across features.

Yes, Flutter BLoC manages live driver location streams by delegating socket access to an injected SocketService and mapping events to a TrackingEntity stream. The TrackingBloc updates the map cubit, animates the camera conditionally, and transitions between connecting, active, completed, cancelled, and error states.

Handling ETA updates and order cancellations in a food delivery client requires mapping eta_updated and order_cancelled socket events to a TrackingEntity stream. The TrackingBloc consumes this stream to update the UI, navigate to rating upon completion, or display cancellation and error states.

An injected SocketService is required for realtime tracking to centralize socket access and prevent duplicated logic across ride and food delivery features. Delegating socket connections through dependency injection ensures proper lifecycle management, stream handling, and clean repository API integration.

Socket.IO for Flutter realtime location tracking requires manual room lifecycle management, joining and leaving order-specific rooms to avoid memory leaks. You must handle connection errors, stream disposal on page exit, and state transitions for cancelled or completed orders to prevent UI inconsistencies.