Mastering MVVM architecture with Kotlin-01.png

tarball.tar.gz

postman

The course focuses on the MVVM (Model-View-ViewModel) architecture in Android development using Kotlin. The MVVM is widely recommended due to its robustness, scalability, and ease of maintenance. It is a valuable skill to have for building high-performance Android applications.

Firstly, you will learn the basics of MVVM architecture and its advantages over other approaches to Android development. Then, you'll start from scratch and create layouts for a news application. Next, you'll use the Retrofit and OkHttp networking libraries and get to familiarize yourself with APIs. You'll get hands-on experience in storing data locally via the Room library. Finally, you'll be introduced to both the repository and ViewModel patterns, as well as how to work with the Paging library and deliver data to our fragments.

By the time you’re done with the course, you’ll be able to use MVVM in your Android projects, interact with APIs, store data locally, and implement pagination.

Mastering MVVM Architecture in Android Development using Kotlin

## What is a ViewModel?

The **ViewModel** is used to store and manage UI-related data while taking the UI controllers’ lifecycle into account. UI controllers can be activities or fragments.

What we mean by ViewModel being lifecycle aware is that it’s able to allow data to survive activity or fragment configuration changes, which may include changing screen orientation or pulling up the keyboard. Thanks to the ViewModel, data is retained to be used during configuration changes when an activity is destroyed and recreated so the user can still have the same data even when the screen orientation changes.

The ViewModel handles all of the logic for the activities and fragments, and the fragment’s job is simply to observe data and present it to the user, making it lightweight and easy to render in the layout. We’ll go through this in more detail in the next chapter.

The flowchart below depicts how the ViewModel controls the flow of data from the models to the view.


# What is a ViewModel?

The **ViewModel** is used to store and manage UI-related data while taking the UI controllers’ lifecycle into account. UI controllers can be activities or fragments.

What we mean by ViewModel being lifecycle aware is that it’s able to allow data to survive activity or fragment configuration changes, which may include changing screen orientation or pulling up the keyboard. Thanks to the ViewModel, data is retained to be used during configuration changes when an activity is destroyed and recreated so the user can still have the same data even when the screen orientation changes.

The ViewModel handles all of the logic for the activities and fragments, and the fragment’s job is simply to observe data and present it to the user, making it lightweight and easy to render in the layout. We’ll go through this in more detail in the next chapter.

The flowchart below depicts how the ViewModel controls the flow of data from the models to the view.


Learn how to write a ViewModel in our project.

Introduction

MVVM Architecture

Layouts

Layout Design Assessment

API

Android Web Services Assessment

Utility Classes

Repository Pattern

ViewModel Pattern

Android Business Logic Assessment

Views

Conclusion

Appendix

ViewModel Pattern

What is a ViewModel?