Tag: riverpod

Use FutureBuilder or StreamBuilder for a self-contained, throwaway async widget. Reach for Riverpod AsyncValue once the result is shared, cached, or mutated. Here is the decision, the gotchas, and runnable code for both. Tested on Flutter 3.44 and flutter_riverpod 3.3.1.

Pick Riverpod for most new Flutter apps in 2026. Choose Bloc for large teams that want an enforced event-driven structure, and keep Provider only for legacy code.

Render loading, data, and error UI from a single AsyncValue in Riverpod 3. Use AsyncNotifier and AsyncValue.guard for mutations, .when() and switch pattern matching for the UI, keep previous data on refresh, and migrate the legacy StateNotifier pattern. Tested on flutter_riverpod 3.x, Flutter 3.44, Dart 3.x.

Step-by-step migration from GetX to Riverpod 3.x in a real Flutter app: GetxController to Notifier, .obs to derived providers, Get.find to ref.watch, Get.to to go_router, plus snackbars, theming, and tests. Tested on Flutter 3.27.1, Dart 3.11, flutter_riverpod 3.3.1.