ReSwift VS TheBinderArchitecture

Check this out: https://github.com/ReSwift/ReSwift

There are some great examples linked to the ReSwift GitHub page: https://github.com/ReSwift/ReSwift

ReSwift is also pretty good!

ReduxKotlin There are a few ports of Redux for KMM. This one might be the best because it is thread safe, which is very nice. The only drawback that I don't love about it is that it doesn't have types for sevral aspacts that feel like they should have types. On the other-hand ReKotlin (which is a port of ReSwift) has a lot of the typing that ReduxKotlin is missing, but is missing the thread safety. It just depends on your use-case.

Great article OP! Im sure you've seen it in your travels, but Ive been using ReSwift and ReSwift-Thunk for async actions and I've had great success - Gonna look into your navigation solution as that was the one part I'm still missing!

I recommend you checkout the code base of ReSwift

Here's an explanation of how to do it. The Binder Architecture

I use RxSwift/RxCocoa and The Binder Architecture. That way View Controllers always show the most recent data from the service.

I'm a big fan of The Binder Architecture. It takes the best of MVVM but without all the boilerplate associated with it.

I use a variation on The Binder Architecture. Another one I like a lot and that works well with SwiftUI is The Composable Architecture.

As far as architecture I found that the MVVM way of making a view model with Inputs and Outputs often made things a bit too abstract when I was starting out. I actually found the architecture described here: https://github.com/DeclarativeHub/TheBinderArchitecture to be easy to understand and more direct when you're starting out and want to actually see things working.

I use Cause-Logic-Effect which is a variation of The Binder Architecture that I developed. CLE is basically like Binder Architecture except my Services are small functions instead of large classes.