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.

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.

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?