Flutter Provider Architecture for State Management | Flutter Provider

preview_player
Показать описание
Flutter Architecture Guide using Provider for state management.

Рекомендации по теме
Комментарии
Автор

If you are getting a dispose exception register the HomeModel as a Factory in the locator and not a singleton.

FilledStacks
Автор

This is THE video for anyone who has tried to use Provider in Flutter and gotten stuck. Pure gold!!

jonathan
Автор

Months ago, I watched this tutorial and had no clue what was going on even though I understood how to use provider. Now I understand every piece of code and reason behind it after gaining more experience in Dart & Flutter. In summary, this is not a beginners video, so don't get overwhelmed. Level up and rewatch in a few month or year or however long it takes for you and comeback. Good job FiiledStacks!

teajay
Автор

WOW!
So I started to learn flutter 3 weeks ago and the last 2 days I was working on an App where I wanted to target exactly the same problem as you did (provider, state management). And its so funny because you built almost exact the same app structure as I did. Even our folder structure is similar and we call the stuff same. Really funny how coders have the same mindset.

Btw: You did not only taught people how to use provider and state management, you also taught us how to structure a large app and keep a nice architecture. THATS GOLD and SO useful.

Btw I usually never comment on videos but you really deserve it. Take my sub!

cloud
Автор

Just what I was waiting for. I used to search for Provider on youtube and medium every day since the I/O presentation. Thank you. You are the best.

iamyogik
Автор

Brilliant! I have read medium posts, watched youtube videos and one paid for tutorial and could not get my head around the concept. I read your article, watched your video and it all falls into place. Not just how it works but how it all fits together in the Flutter framework. Thank you very much.

johnjamesflashman
Автор

So impressive. Just starting with Flutter but this is exactly what I have been looking for coming from messy code tutorials. Thank you!

anjena
Автор

Can't believe something like this is free🙏Thank you so much!

soepet
Автор

I can't stop viewing this video over and over again, never seen such systemically organized code.

jondoe
Автор

Thank you! You have an excellent presentation style, and you explain content in a thorough manner.

phutchins
Автор

Can We agree that this architecture needs to be the number ONE recommended architecture on FlutterDev? @FilledStacks is using Provider (Recommended state management technique), so this architecture could be the Recommended way to structure our apps. No craziness, easy to follow, easy to implement, easy to maintain. How do we make this happen?

elherediaenc
Автор

I love flutter now because of you.. I think Google's developers need to learn something to you.. Thank-you so much

akashkumardas
Автор

Great video! Keep up the awesome work 🔥

RobertBrunhage
Автор

Legends!! Exactly what i've been searching for days.. Well done guys! please keep up the great posts :)


Coming from Mvvm in Xamarin this structure brings in alot of the architecture and best practices I've come to appreciate and value

cass
Автор

Best video of Provider by far on youtube

samraanali
Автор

Searching examples of the flutter provider has arrived here.
Excellent video very well explained.
I will look forward to your next videos.


Thank you.

pedrobros
Автор



That's too good...👌
I will change my entire app progress of last two weeks. After what I just watched.

fahadmdkamal
Автор

Excellent video, however, I have a few suggestions to make it better:

1) use interfaces for the services. It's needed when you start making tests, or even during development, sometimes we want a mocked service registered to work on something we want specifically to work with (let's say, edge cases).

2) for a viewstate you might need specific states per page, in this case I use an enum per page and a single boolean for "isBusy" doesn't change too much of what you did and gives the flexibility to add more than 2 stages. So, if isBusy is true, the view is busy, otherwise it is idle however, the page's state can be anything depending on your app's logic (in my case, I have an upload button that creates a state "uploading" which will add a small message, however, the page is not busy, I can still use the rest of it except for the upload button).

Now, a couple of questions'

Isn't the provider rebuilding the whole page? I mean, I don't need to rebuild the login title, but when it triggers the setState, isn't it rebuilding it? I know is not much, just one text, but image that this page has a lot more that I don't want to rebuild, how should I handle this?

nosmirck
Автор

Thank you, this video was very informative. I needed several hours to process all the info within...
But I'm very confused as to why you decided to not inject the AuthenticationService for obtaining the User id in order to get the posts. you mention that "it does not make sense", but I don't really understand the reasoning. I have the following questions:
1) How do you decide when to use a Stream or when to inject a service? do you follow any particular rules?
2) What happens if you want/need to listen to multiple streams in your app? Do you surround your StreamProvider with another StreamProvider and so on for as many streams as you need? Does that even work?

ziritrion
Автор

Awesome tutorial!! A little hard to follow because the speed of the explanation, but it was valuable anyways. I would like to learn how to prevent the user to go to login route when already logged in, and learn more about the locator technique used in this app tutorial.

aislanarislou
visit shbcf.ru