The Model-View-ViewModel (MVVM) pattern and the UI

A common challenge in Unity development is to find elegant ways to decouple components from each other, especially when developing the UI because it involves UI logic and UI rendering. Model–View–ViewModel (MVVM) is a software architectural pattern that helps developers separate the ViewModel, which is the UI logic, from the View, which is the UI graphics. In this section, we will explore how to implement an MVVM pattern in Unity.

Figure 3.40 – MVVM

As its name suggests, MVVM consists of three parts:

• Model: This refers to the data access layer, which can be Database, or PlayerPrefs, which stores player preferences in Unity, and so on.
• View: This represents the Unity UI. It needs to be a Unity component that inherits from MonoBehaviour and is attached to the UI object. Its main role is to manage UI elements and trigger UI events, but it does not implement any concrete UI...