Provider Skill
This skill defines how to correctly use the provider package in Flutter applications.
1. Provider Types
| Provider | Use for |
|---|---|
Provider | Exposing any immutable value |
ChangeNotifierProvider | Mutable state with ChangeNotifier |
FutureProvider | Exposing a Future result |
StreamProvider | Exposing a Stream |
ProxyProvider / ChangeNotifierProxyProvider | Objects that depend on other providers |
2. Setup
MultiProvider(
providers: [
Provider<Something>(create: (_) => Something()),
ChangeNotifierProvider(create: (_) => MyNotifier()),
FutureProvider<String>(create: (_) => fetchData(), initialData: ''),
],
child: MyApp(),
)
- Use
MultiProviderto group multiple providers and avoid deeply nested trees. ChangeNotifierProviderautomatically disposes the model when it is no longer needed.- Never create a provider's object from variables that can change over time — the object won't update when the variable changes. Use
ProxyProviderinstead. - If you have 150+ providers, consider mounting them over time (e.g., during a splash screen) rather than all at once to avoid
StackOverflowError.
3. Consuming State
Always specify the generic type for type safety:
// Listen and rebuild on change
final count = context.watch<MyModel>().count;
// Access without listening (use in callbacks)
context.read<MyModel>().increment();
// Listen to only part of the state
final count = context.select<MyModel, int>((m) => m.count);
Use Consumer<T> or Selector<T, R> widgets when you need fine-grained rebuilds and cannot access a descendant BuildContext:
Consumer<MyModel>(
builder: (context, model, child) => Text('${model.count}'),
child: const ExpensiveWidget(), // rebuilt only once
)
Selector<MyModel, int>(
selector: (_, model) => model.count,
builder: (_, count, __) => Text('$count'),
)
4. ProxyProvider
Use ProxyProvider or ChangeNotifierProxyProvider for objects that depend on other providers or values that can change:
MultiProvider(
providers: [
Provider<Auth>(create: (_) => Auth()),
ProxyProvider<Auth, Api>(
update: (_, auth, __) => Api(auth.token),
),
],
)
5. Rules
- Do not access providers inside
initStateor constructors — use them inbuild, callbacks, or lifecycle methods where the widget is fully mounted. - You can use any object as state, not just
ChangeNotifier; useProvider.value()with aStatefulWidgetif needed.
6. Debugging
Implement toString or DiagnosticableTreeMixin to improve how your objects appear in Flutter DevTools:
class MyModel with DiagnosticableTreeMixin {
final int count;
MyModel(this.count);
@override
String toString() => 'MyModel(count: $count)';
}
7. Migration: ValueListenableProvider
ValueListenableProvider is deprecated. Use Provider with ValueListenableBuilder instead:
ValueListenableBuilder<int>(
valueListenable: myValueListenable,
builder: (context, value, _) {
return Provider<int>.value(
value: value,
child: MyApp(),
);
},
)