Wrap-up

What we have learned?

We have learned a lot concerning building a well-ordered and organized application that is reusable and flexible using the MVVM architecture. But apart from the architecture itself, we have learned a couple of valuable things along the way, which are mostly Jetpack components.

Let’s highlight them.

• Pagination: In this lesson, we saw how pagination helps load a large dataset by dividing it into smaller chunks, thus making a better use of system resources, including the bandwidth.

• Room: We harnessed the power of the Room library for SQLite mapping by using annotations to write fewer lines of code to persist data locally for offline view, thanks to its easy integration with LiveData to return queries directly. We also looked at its subcomponents: Entity, DAO, and Database, which have highly used annotations to generate code in the background automatically.

• ViewModel: ViewModel is the most critical component of an application because it’s the one that efficiently supports data for the UI components. It manages and handles UI-related data and is also lifecycle-aware to allow data to survive configuration changes, making it a mandatory component for best practice in software design.

• Navigation Component: We learned how to implement the navigation framework to manage navigations and complexities that come with handling fragment transactions within the application, which includes navigation across, back, and into the application where we looked at its three key parts.

  • Navgraph ...