connectivity_plus: network type is not internet reachability

connectivity_plus is useful because it focuses on connectivity streams, offline UX, reachability checks, and platform nuance. The important engineering move is to place the package behind a clear boundary, so your Flutter UI depends on a stable capability rather than a vendor-shaped API.

What the library should own

• Keep package calls inside a named adapter or feature boundary.
• Make lifecycle, errors, and loading state part of a testable contract.
• Expose only the capability the app needs; hide implementation details from the whole tree.

A focused starting point

final subscription = Connectivity().onConnectivityChanged.listen((types) {
  final hasTransport = types.any((type) =>
      type == ConnectivityResult.wifi || type == ConnectivityResult.mobile);
  banner.show(hasTransport ? 'Online' : 'Offline');
});

// Cancel subscription in dispose().

Production checklist

1. Read the README and changelog for the exact version you pin.
2. Add one test for lifecycle, failure, and app background/foreground behavior.
3. Verify every platform your product supports, not only the developer machine.
4. Record ownership, upgrade cadence, and rollback notes in the repository.

Common pitfall

Do not use connectivity type as proof that an API call will succeed; confirm with a request or health check.

Takeaway

A good open-source library does not replace architecture. It makes one difficult boundary clearer, observable, and easier to replace.