CLE-Architecture-Tools VS TheBinderArchitecture

You might find my ErrorRouter class to be handy. It reroutes errors to a single subscription so they don't affect the observable chains at all.

I do this with RxSwift and my CLE library. Using those you can do something like this:

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.

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.