MVVM Insights | Sumble

What is MVVM?

MVVM (Model-View-ViewModel) is a software architectural pattern that facilitates the separation of the development of the graphical user interface (the View) from the development of the business logic or back-end logic (the Model) through a ViewModel. The ViewModel is responsible for exposing data objects from the Model that are easily consumed by the View. The View binds to properties on the ViewModel, which in turn exposes data contained in the Model. This separation of concerns improves testability, maintainability, and reusability of the code.

Find organizations using MVVM on Sumble →

What other technologies are related to MVVM?

MVVM Competitor Technologies

MVP

Model-View-Presenter is an alternative architectural pattern to MVVM.

mentioned alongside MVVM in 79% (6.9k) of relevant job posts

VIPER

VIPER (View, Interactor, Presenter, Entity, Router) is an alternative architectural pattern to MVVM, especially prevalent in iOS development.

mentioned alongside MVVM in 71% (2.5k) of relevant job posts

Clean Architecture

Clean Architecture is an architectural philosophy which competes with MVVM as the root architecture.

mentioned alongside MVVM in 46% (3.6k) of relevant job posts

MVI

Model-View-Intent is an alternative architectural pattern to MVVM.

mentioned alongside MVVM in 85% (1.6k) of relevant job posts

MVC

Model-View-Controller is an alternative architectural pattern to MVVM.

mentioned alongside MVVM in 11% (11.3k) of relevant job posts

MVVM Complementary Technologies

Retrofit

Retrofit is a type-safe HTTP client for Android and Java. It can be used in the Model layer of an MVVM architecture to handle network requests.

mentioned alongside MVVM in 38% (2.7k) of relevant job posts

Coroutines

Kotlin Coroutines can be used for asynchronous programming within the MVVM architecture, especially in the Model layer.

mentioned alongside MVVM in 43% (2.3k) of relevant job posts

Jetpack Compose

Jetpack Compose is a modern toolkit for building native Android UI. It complements MVVM by providing a declarative way to build the View layer, often used with LiveData or StateFlow from the ViewModel.

mentioned alongside MVVM in 29% (3.2k) of relevant job posts