Performant, sleek and elegant.
In model-view-view model (MVVM) architecture the view model observes the model and provides data for the view by transforming it when needed. When the user interacts with the view and changes the data in it then the view model's responsibility is to propagate those mutations back to the model object. Therefore, the important part in …
Continue reading "Observing a KVO compatible model in SwiftUI and MVVM"
A while ago I wrote about using MVVM in a SwiftUI project. During the WWDC’20 Apple announced @StateObject property wrapper which is a nice addition in the context of MVVM. @StateObject makes sure that only one instance is created per a view structure. This enables us to use @StateObject property wrappers for class type view …
View models in MVVM are responsible of making the model suitable for presenting by a view. Quite often model objects themselves have properties which can be directly presented by the view. SE-0195 added dynamic member lookup types. Using @dynamicMemberLookup we can add all the model object's properties to the view model itself. Result, model.name is …
Let's build a simple app using MVVM (model-view-view model) where every SwiftUI view has its own view model. It's going to be an app with two views: list of movies and add a movie view what utilises Form view. Added movies are stored in MovieStore which is shared by the two view models. We will …
