Book Image

Clean Android Architecture

By : Alexandru Dumbravan
Book Image

Clean Android Architecture

By: Alexandru Dumbravan

Overview of this book

As an application’s code base increases, it becomes harder for developers to maintain existing features and introduce new ones. In this clean architecture book, you'll learn to identify when and how this problem emerges and how to structure your code to overcome it. The book starts by explaining clean architecture principles and Android architecture components and then explores the tools, frameworks, and libraries involved. You’ll learn how to structure your application in the data and domain layers, the technologies that go in each layer, and the role that each layer plays in keeping your application clean. You’ll understand how to arrange the code into these two layers and the components involved in assembling them. Finally, you'll cover the presentation layer and the patterns that can be applied to have a decoupled and testable code base. By the end of this architecture book, you'll be able to build an application following clean architecture principles and have the knowledge you need to maintain and test the application easily.
Table of Contents (15 chapters)
Part 1 – Introduction
Part 2 – Domain and Data Layers
Part 3 – Presentation Layer

Inspecting module dependencies

In this section, we will analyze the dependencies used across the different modules in the application created in the previous chapters.

Following Exercise 09.01 – Transitioning to MVI from Chapter 9, Implementing an MVI Architecture, we now have a fully functioning application split into separate modules, representing different layers. We can analyze the relationship between the different modules by looking at the dependencies block in the build.gradle file in each module and focusing in particular on the implementation(project(path: "{module}")) lines. If we were to draw a diagram, it would look like the following:

Figure 10.1 – A module dependency diagram for exercise 09.01

In the preceding figure, we can see that the :domain module, which is part of the domain layer, is at the center, with the modules from the other layers having a dependency toward it. The :app module is responsible for assembling...