ReSwift 1.0.0: Unidirectional Data Flow in Swift(github.com)
github.com
ReSwift 1.0.0: Unidirectional Data Flow in Swift
https://github.com/ReSwift/ReSwift/tree/master
4 comments
Would you say it's good enough/stable enough for production use yet? I've been keeping an eye on ReSwift for a while now, but i've been hesitant about using it for anything serious because there doesn't seem to be any real apps out in the wild using it yet (AFAIK). Would really like to model my app state with the Redux-like pattern, from a single source of truth.
It's in use in production. We are using it in our internal apps now. Some apps in Japan have been appearing in the App Store using it, such as: https://itunes.apple.com/jp/app/id1088140538.
I would recommend trying to build an app using a DIY store following the principles first to get a really good feel for how it fits in. Moving from DIY -> ReduxKit -> ReSwift has been really easy.
I would recommend trying to build an app using a DIY store following the principles first to get a really good feel for how it fits in. Moving from DIY -> ReduxKit -> ReSwift has been really easy.
Yes, I would consider it production ready. The library itself is really small, which means you don't paint yourself in a corner by using it.
We're still early on, so there are many different implementation patterns that might evolve around the core library but in my experience and that of other devs I've talked to it is already a pretty good step forward from an MVC approach.
We're still early on, so there are many different implementation patterns that might evolve around the core library but in my experience and that of other devs I've talked to it is already a pretty good step forward from an MVC approach.
Yes. I am about to ship an app with it and am working on a second one also using it.
I'm still trying to wrap my head around it after having read the "Getting Started" guide.
How do you handle async items, like service calls? Do you perform them in your reducers or elsewhere?
How do you represent persistence if you want to say, store something in NSUserDefaults. What abstraction would you use around something like that?
How do you handle async items, like service calls? Do you perform them in your reducers or elsewhere?
How do you represent persistence if you want to say, store something in NSUserDefaults. What abstraction would you use around something like that?
I love the approach. Been using it for my latest projects and the results are amazing: having a clearly defined app state at all times makes lots of view updates so much easier.
Really awesome framework! Have been using it for my latest project and is especially great if you have done some Redux for the web.
I wrote a pub sub that I use like this. Not sure I need everything else. Dispatching strings (enums) works as a charm. https://github.com/seivan/NotificationHub
It's a nice take on unidirectional data flow as it applies to the Swift type system.
It brings a lot of clarity to the design. If I want to know the state involved in a view it's all explicitly stated in one place. If I want to know where state is manipulated, that's in the reducer.