This pattern splits the User
Interface code into 3 conceptual parts - Model, View and ViewModel.
Model
This is a set of classes representing the data coming from
the services or the database.
View
This is the code corresponding to the visual representation
of the data the way it is seen and interacted with by the user.
ViewModel
serves as the glue between the View and the Model.
It wraps the data from the Model and makes it friendly for being presented and
modified by the view. ViewModel also controls the View's interactions with the
rest of the application
Join MindStick Community
You need to log in or register to vote on answers or questions.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Model-View-ViewModel (MVVM)
This pattern splits the User Interface code into 3 conceptual parts - Model, View and ViewModel.
Model
This is a set of classes representing the data coming from the services or the database.
View
This is the code corresponding to the visual representation of the data the way it is seen and interacted with by the user.
ViewModel
serves as the glue between the View and the Model. It wraps the data from the Model and makes it friendly for being presented and modified by the view. ViewModel also controls the View's interactions with the rest of the application