How should you properly implement automatic reconnection logic for a WebSocket connection that genuinely gets unexpectedly dropped, such as when a device briefly loses its internet connectivity or moves between different networks?

Since a WebSocket connection can genuinely be unexpectedly dropped for several genuinely different reasons, including a device briefly losing connectivity or a server itself being genuinely temporarily restarted, a genuinely robust implementation should properly listen for the connection's own onDone or onError callbacks and automatically attempt to properly reconnect after a genuinely reasonable short delay, ideally using an exponential backoff strategy that gradually increases that particular delay between each successive reconnection attempt, ensuring your app genuinely recovers gracefully from a temporary connectivity interruption without requiring the user to manually restart the entire app themselves.

void connectWithRetry() {
  channel.stream.listen(
    onData,
    onDone: () => Future.delayed(Duration(seconds: 3), connectWithRetry),
    onError: (e) => Future.delayed(Duration(seconds: 3), connectWithRetry),
  );
}