Pragmatic State Management Using Provider (The Boring Flutter Development Show, Ep. 24) 

I love this show. 1) I am able to learn a lot while watching it. The context you get from watching you guys think about why/when to use a certain technique is really valuable and you don't get that in little snippet videos. 2) It's really reassuring to see you guys actually have to "think" about what to use. In the world of hyper-editted videos, it's easy for someone to come off as having zero struggle or thought process. Seeing you guys take a pause to consider the implementation is a nice reflection of the reality of programming - we're not just typing hundreds of lines of code every minute, flawlessly slamming out the perfect implementation.

I'd love for there to be another Boring Show with working on provider from scratch

That's exactly what I was looking for where refactor code having bloc pattern to provider pattern. It's really a very nice vblog on state management using provider. Though it names boring flutter development, in actual it was very interesting and I really enjoyed it. There was much learning along with the provider implementation. Thank you Flutter team, of course, Matt and Filip.

This stands the test of time. I laughed out loud a lot, especially in the beginning. Thanks for just wading into it and demonstrating good coding practice during realtime refactoring. I came here because my page keeps getting the MyApp's MaterialApp's context and then can't see the Providers that reside lower in the tree. Anyway, now I'm gonna watch it again.

Please do a show on State Management again. This was not informative at all. Demonstration of any architecture with an app that has 1-2 screens is easy. But how will the architecture scale in medium to large scale apps. We would love to hear what architecture solutions are used by big apps such as Google Ads, Hamilton, Reflectly etc.

Good paired programming. Need more videos like this. Off the cuff and trying to fix things on the fly.

Best episode so far, loved it

Apart from the excellent content, I ❤️ Matt's t-shirt

Having some friendship with RxJs and RxJava, This episode was an interesting one to me among many others. You guys are great. One Request - Please create an another episode on providers for medium to large application from scratch with some detailed info on it.

Thanks for such a boring show 😆. Have been waiting for this topic. Hope you'll continue on this in next episode. I think you guys should try live boring show so that we can also participate.

I need that dart t-shirt Matt's rockin.

the best show ever . better than netflix

Very informative!

I love to see you guys struggle as much as I do (as a flutter newbie).

Great video about Provider. I have a question in my mind though. I would be happy if you can help me to understand some point. I have an app and I am using provider to handle the authentication. I wrapped my MaterialApp with ChangeNotifierProvider. Apart from that I have an Auth class that extends ChangeNotifier and I notify the listeners after the user is logged in or I check if there is a current user(local storage) in the constructor. Depending on the user state I return appropriate widget(Login screen, main screen etc.) It works perfectly but when I use Navigator to push new routes, The ChangeNotifier builder part where I wrapped MaterialApp rebuilds everytime even there is no change with the data. I am not calling notifyListeners either. So I dont't understand why pushing new routes triggers that part. To give an example I have a widget in the main screen with a FutureBuilder which returns a list. When I click to a list item it pushes to a detail view. When I go back, it rebuilds the previous widget so FutureBuilder is fired again. I assume it is rebuild because it is a descendent of MaterialApp and that part is being rebuild causes my main screen to rebuild too.

Watched your conference guys, and that was great. I used provider on my app. It was simple to implement and made so much sense. Looking forward to watching this one

Can you update the documentation on use cases of different providers?

Hey with using StreamProvider.value, do you have an example of how to use the the "catchError" property, I can't find anything online besides the official documentation which I can't translate to a real world example. Help! :)

It's not often that I feel so good after watching the notification for a "boring show".

hi. should i create class called model to put data/vars into it to keep provider is simpler. look like MVP or MVVM ?

that dart side T-shirt is kicking all kinds of asses

Great show guys, full of laughs 😂

The much awaited show 💃🏽

Please do an episode on local notification, and how the provider framework works when you try to tap on the notification pop up to open to a specific page. This would be very helpful!

it's not boring but awesome we can learn alot about provider I wish I can code like u all

uau amazing!!

This Notifier reminds me A LOT an MVVM ViewModel from C#... How do they differ in architecture?

i have one question What is the overhead of sending a object down the stream so for example i have an application with arround 25 widgets Or arround 12 screens. i set the initial value at screen 3 and get and use the value at screen 10-12 The whole process of passing object from 3 to 10 using context will have some overhead What and how much exactly will be the overhead for moving 3 to 10 without using it once Thanks

Why did you initialized the cache Map() in an initialization list at the constructor, and not at the field's declaration? It doesn't use anything from the constructor.

i really wanna know which is better this approach or bloc pattern for state mangement

Make a movie about the 3.0 provider. There are many changes, for example ProxyProvider, how to use it and when. BTW nice video 😉

Hi there! I started Flutter with the provider and I'm pretty comfortable with this. But now my company is asking me to use BloC, but I really don't like BloC, and I'm getting a hard time working with the bloc. So should I use bloc or just say to my company that I can't use bloc. Please suggest should I use bloc or not.

Does the information proceed that the Provider should not be used in medium and large projects because of the limitation of ChangeNotifier in relation to the number of listiners that it can answer? Sorry for bad writing, I don't speak English

How does the provider work in situations where i want to use Navigation-Routes? My Provider isn't there available anymore. How do i reach it there?

I'd like to know which macbook model you're using as a flutter developer and how it's going on so far with you?

Thanks guys!!! Officially switched to provider from scoped_model!! Thanks flutter team

When rapping the whole app with a ChangeNotifierProvider, and say for example a specific value that’s being displayed in a text changes, does the whole ui get rebuilt or only that specific textview?

Oh My fav Matt heree finally.........:)))) Awesome!!!!!!

Could you guys do an example of how to implement FirebaseCloudMessaging with state management and provider? I'm struggling a bit with it since I want to use the same architecture you're showing. :)

Where can I find source code to refer after watching the video ?

Thank you for this video but the current version of provider is 3.0.0 but the video is 2.0.1 :(

Is there ANY advantage of Bloc vs Provider in reality?

Matt, where did you get that T-Shirt! Its awesome haha! I want one.

You guys should review the captions, someone captioned "Flutter" as "Photo"

provider now is in version (4.x.x) and hopefully, you make video for this and in a way more forcesing on provider itself ''Sorry for bad English "

Awesome vid. They sitting there for almost an hour. Hard working i guess

stackoverflow.com/questions/57559489/flutter-provider-in-initstate Same issue but I need to pass 2 parameters from the widget to the method in Provider. Couldn't find a proper answer yet. Any help is appreciated.

I am definitely going to try Provider. Bloc has been really hard to implement small features.

Could you do In-App Purchases next? It's one of the most important topics.

How old is this? Provider 3.0 has been out for a while now.

I started thinking that it was an extended version of the IO talk, but instead of a nice way into Provider it was actually a painful guide of something you advised not to do in the talk: which is porting to Provider an app that was already working perfectly in Bloc. As a result it requires knowledge of both (BLoC and Provider) and was a pain to watch. Don't get me wrong, I love the show and I follow the whole series. But the question that remains in my mind after this process is whether I really learned something or got even more confused... was it worth it? Maybe a better move would be porting from hardcore bloc to flutter_bloc lib instead. And for provider lib, something from scratch would more helpful to 'think provider' from the beginning. Of course, that is either a branch of this show or we will have to wait until a new series start. But thanks anyways. Sincerely.

can anybody explain please @25:02 when the context is replacing with the underscore . why ?

As Matt admitted, this is quite struggling and confusing, possibly because we are refactoring from stream pattern to listener pattern. However, after watching this show, I have an impression that Provider is doing more than one things at the same time (SOLID anyone?), one is dependency injection, and two is dataflow/state management. Doing DI, Provider is better and/or easier than InheritedWidget, at least with proper `dispose`. This is the reason it is said that Provider can be used with BLoC, and creates some confusion. Doing state management, it takes a different approach than BLoC (which is basically stream/reactive/Rx), so the learning curve to flutter can be gentler for those who don't have the background in reactive functional

So, for state management, is it a Flutter best/preferred practice to use, especially in a new app, provider instead of BLoC? I see even Flutter documentation documents provider for simple state management: flutter.dev/docs/development/data-and-backend/state-mgmt/simple

why you don't advise on checking other patterns like MVP or clean architecture? is it at antipattern somehow to Flutter react world? I'm having some issues with coworkers were they argue that this is now how Flutter should work because you advise Bloc or Provider instead of other's

I need this dart shirt 😕

Seeing Google guys using apple is fun 😂

How are errors handled. Like a Network request failed

Great video, please share the code

Hi max :)

That's shortest boring show ever~ Let's bore people further. hahahaha

why is it that every time I start a new app, I need to watch this video :(

Why provider's version is 2.0.1 now ?

link to the pull request github.com/filiph/hn_app/pull/7

I need that shirt! Where can I find it?

Well first at all, please use a black theme for your IDE 😅. Now It was a great refactoring example from Bloc to Provider but, since I'm new in flutter and I'm already starting with couple hours with Bloc, there are some things confusing me, can I really completely replace a complex bloc project with Provider. I was wondering how I’ll deal with certain logic like showing modals, snackbar, notifications, etc. Because all the examples that I found are straightforward. Or is provider not intended to solve such things? It’s just a DI system? PD: 1:01:55 Each one of us has been there 😂

it only works on debug mode, on release it doesn't work unless you kill the app and reopen.

Have a look at state_rebuilder

53:59

Why no Chinese subtitles？

Matt's Flutter apparel making me jealous as usual lol

what exactly is BLoC stand for

Amazing...Videos..Love it from Pakistan..Peace out..TC #flutter #love_flutter #pakistan #dart #provider

can you please go dark mode?

39:10 why ids is final . i usually use var :(

mark

This looks more or less like scopedModel to me

I clicked that link so fast!

Guys, I love the show, but I honestly think it could be a lot better if you had some preparations beforehand. This way you could show us all the struggles that you had, but just taking a small amount of time, while coding the best solution at the show.... Instead of just trying to make things work in one hour, and not showing us the proper way to solve things. I don't mean to be harsh, I just think the show could be better, more informative this way :)

Wait a minute ! they are using macbooks !

Last

koplak 😁

While Provider is good for smaller apps, I constantly find that it gets cumbersome when working with multiple developers and for really large Apps. Redux is definitely the way to go for such Apps.

Oh, I wish I could understand something :’( I guess I need to start from scratch again...

Old record. Provider version now is 3. 😁

tutorial on how to program without google haha

first

The most confused boring show

Sorry but this video provides nothing beneficial to me. Why don’t you guys go with somewhat the basics?

To those looking to quickly learn and implement clean state management in flutter, skip learning this whole layer and check out flutter_redux.

Too much talking about unrelated stuff. Please stick to the topic and this will make the video shorter. We need to spend time coding our own apps rather than watching one-hour videos. Thanks!