3 ms·
OP mentions the Provider package [1] wasn't around when they did the Flutter version. That is really too bad, because it is absolutely the best way to manage st
by latchkey 7y ago
OP mentions the Provider package [1] wasn't around when they did the Flutter version. That is really too bad, because it is absolutely the best way to manage state in Flutter. It makes things so much easier and cleaner than the other methods.
[1] https://github.com/rrousselGit/provider https://github.com/rrousselGit/provider
Edit: I probably would have even gone back and refactored the app to use Provider before publishing the article. =) That would have been a nice additional bit of information for the reader.
- rhlsthrm 7y agoLooks like lots of things didn't exist then for each framework which made a lot of the issues he encountered easier: SwiftUI, React Hooks/useContext, Jetpack. I'd like to see a revisit of this whole project.
- verttii 7y agoWow this looks interesting, I don't know why it has slipped right past me so far.
- cgs 7y agoI was glad I found Provider after almost diving into BLoC. The less boilerplate and context switching the better.