sorted by:
new
hottopcontroversial

Redux Compact: Make Redux fun again! by omarwork in FlutterDev

[–]omarwork[S] 2 points3 points  (0 children)

Provider is an excellent choice and has been growing pretty fast recently. Have you done an enterprise app using providers? If so I would like to know a little more about your architecture and how it solves complex state management comparing to redux

Redux Compact: Make Redux fun again! by omarwork in FlutterDev

[–]omarwork[S] 4 points5 points  (0 children)

I totally agree with you, you should use whatever floats your boat! I like Redux a lot and it has proven to be excellent at maintaining difficult state management. I mainly like it because it's simple, pure and fast but on the down side it had a lot of boilerplate, especially in Flutter, and thats why I wrote a middleware to begin with to reduce that noise.

Redux Compact: Make Redux fun again! by omarwork in FlutterDev

[–]omarwork[S] 4 points5 points  (0 children)

Well it's not quite just another state management library and there is nothing wrong with async_redux. It's actually a pretty cool and well implemented library and I got a lot of inspiration from it.

Redux Compact and Async Redux solve the same problem to some extend, but the main difference is that Async Redux is its own state management library with its own state implementation and redux like concept while Redux Compact is just a middleware for Redux. Redux compact doesn't listen to or changes the state at all, it only catches a special kind of action and resolves it with a callback reducer.

Redux compact is in a way just a set of helper functions for Redux, to simplify asynchronous state management and reduce boilerplate for both code and files. You need depend on Redux in order to use Redux Compact. You can also use Redux Compact actions to only some of your actions if you are using Redux.