Book Image

Kickstart Modern Android Development with Jetpack and Kotlin

By : Catalin Ghita
5 (1)
Book Image

Kickstart Modern Android Development with Jetpack and Kotlin

5 (1)
By: Catalin Ghita

Overview of this book

With Jetpack libraries, you can build and design high-quality, robust Android apps that have an improved architecture and work consistently across different versions and devices. This book will help you understand how Jetpack allows developers to follow best practices and architectural patterns when building Android apps while also eliminating boilerplate code. Developers working with Android and Kotlin will be able to put their knowledge to work with this condensed practical guide to building apps with the most popular Jetpack libraries, including Jetpack Compose, ViewModel, Hilt, Room, Paging, Lifecycle, and Navigation. You'll get to grips with relevant libraries and architectural patterns, including popular libraries in the Android ecosystem such as Retrofit, Coroutines, and Flow while building modern applications with real-world data. By the end of this Android app development book, you'll have learned how to leverage Jetpack libraries and your knowledge of architectural concepts for building, designing, and testing robust Android applications for various use cases.
Table of Contents (17 chapters)
1
Part 1: Exploring the Core Jetpack Suite and Other Libraries
7
Part 2: A Guide to Clean Application Architecture with Jetpack Libraries
13
Part 3: Diving into Other Jetpack Libraries

Summary

In this chapter, we gained an understanding of how Room is an essential Jetpack library because it allows us to offer offline capabilities to our applications.

First, we explored the core elements of Room to see how a private database is set up. Second, we implemented Room inside our Restaurants application and explored how to save and retrieve cached content from the local database.

Afterward, we discovered what partial updates are and how to implement them to preserve a user's selections within the app.

Toward the end of the chapter, we understood why having a single source of truth for the application's content is beneficial and how that helps us in edge cases such as a system-initiated process death.

In the next chapter, we're going to dive deeper into various ways of defining the architecture of our applications by exploring architectural presentation patterns.