Flutter Provider vs BLoC

Provider can be somewhat difficult to explain. The package author, Remi, has described it as a mix between State Management and Dependency Injection . At his talk at Flutter Europe in 2019, he quoted another Flutter community usual, Scott Stoll, who called is ‘Inherited Widgets for humans’.

The answer is simple, and the power of the Provider package is in its simplicity: Providers allow to not only expose a value, but also create/listen/dispose it . When you place a Provider widget in your widget tree all the Childs of the Provider will have access to the values exposed by it.

Redux is also a state management approach. For dealing with local state BLoC is best recommended , while for Global state BLoC maybe used when the app is simple and not much complex but not recommended. For Global state, Redux is highly recommended.

So here we can compare the StreamBuilder in Bloc with Consumer in Provider. The difference is that StreamBuilder listens to the stream and fetches the model on every change to rebuild the widget . But Consumer listens as soon as notifyListeners() executes inside the provider class.29 Haz 2020

BlocProvider is a Flutter widget which provides a bloc to its children via BlocProvider. of<T>(context) . It is used as a dependency injection (DI) widget so that a single instance of a bloc can be provided to multiple widgets within a subtree.

When compared bloc with provider. Bloc is a little bit difficult and has lots of boilerplate code. But Bloc is better for complex apps .