SwiftUI does not follow MVC architecture. This means when you create a brand new application in Xcode 11 and enable SwiftUI, it does not create any controllers. This does not mean that you can’t use MVC design pattern with SwiftUI, it simply means maybe a different pattern (MVVM) can better suite your needs.
MVVM programming with View Models is the new pattern that Apple is recommending developers follow after WWDC this year. I want to go over a very quick example of setting up an ObservableObject with Published properties to trigger UI refreshes in your app.
MVVM programming with View Models is the new pattern that Apple is recommending developers follow after WWDC this year. I want to go over a very quick example of setting up an ObservableObject with Published properties to trigger UI refreshes in your app.
One of the biggest idea for having MVVM is that most of data flow can be testable. Data binding in view layer by SwiftUI is awesome. However, this project has view model layer to make it testable as much as possible.
Three different architectures (Model-View, Redux, MVVM) for using SwiftUI implemented at the example of a chat app
Improves upon the original Weather app using SwiftUI. It allows users to call up the current weather and daily forecast for a particular location using the Dark Sky API.
Example project of SwiftUI and Combine using MVVM architecture pattern.