3 ms·
> you can use MVVM But they are still a deviation from the model the SDK was designed for. The original Apple SDKs are totally bog-standard MVC models. If I tr
by ChrisMarshallNY 4y ago
> you can use MVVM
But they are still a deviation from the model the SDK was designed for. The original Apple SDKs are totally bog-standard MVC models. If I try anything other than that, the code complexity increases a lot (especially with VIPER).
I think that a lot of these models were developed to allow projects that were really supposed to be doable by one experienced person, to be broken into something for a team of relatively inexperienced people. That's not necessarily a bad thing; but it's not how I work.
I like keeping things simple; even though it never ends up simple (See "Programmer's Credo," above).
> but you can use observable objects & such with UIKit
Yeah, but it's not really "native" support, like AppKit. SwiftUI has it baked into its DNA.
- ericlewis 4y agoit is a really well established pattern now a day tho and most iOS eng i come across know how to work with it. also totally agree on keeping it simple, but I spend about 6 months designing a codebase we could bring anyone up to speed on and it has worked!