Post

Replies

Boosts

Views

Activity

Reply to Stop using MVVM for SwiftUI
First of all, thank you Appeloper for all the effort you put on the whole post! I love this kind of discussion because it always bring good questions and force us to remember why we use what we currently use. Another reason for being on your side is because some people treat the "Clean Architecture" as a bible that shouldn't be questioned and you are bringing those questions. To be honest, I agree with a lot of things you showed us but I'm still skeptical on how those things would apply for a big project. Imagine an app that has hundreds of entities and complicated logics, wouldn't those translate to thousand lines of code in a single entity? Just to be clear, I'm asking these questions with a totally open mind, as I said, I think you have something there and I'm trying to sell it in a new project we are building. Some points that other people brought up: Architectures should be technology agnostic, "MV" is pretty tied to how SwiftUI works. MVVM is easier to implement and separate logic Other arch like VIP/Clean are easier to test business logic and have more reusable components The UI engineer from Apple told that this is a bad approach Also you are not proposing a whole new architecture, just a way to build apps in SwiftUI. Some people are very tied to Software Development as it was 50 years ago, with spec documents and boring stuff like that, but on most companies that's not how it works, it's us developers trying to build the next big thing and making it maintainable and testable.
Nov ’22