Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Clean Android Architecture
  • Toc
  • feedback
Clean Android Architecture

Clean Android Architecture

By : Alexandru Dumbravan
4.5 (6)
close
Clean Android Architecture

Clean Android Architecture

4.5 (6)
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)
close
1
Part 1 – Introduction
6
Part 2 – Domain and Data Layers
10
Part 3 – Presentation Layer

Chapter 10: Putting It All Together

In this chapter, we will analyze what we have done so far in the previous chapters and look at different ways we can improve the layers of the application. Later, we will explore the benefit of clean architecture when we integrate instrumented testing into the application, where we will swap the data source dependencies with mock dependencies to ensure the reliability of the tests.

In this chapter, we will cover the following topics:

  • Inspecting module dependencies
  • Instrumentation testing

By the end of the chapter, you will be able to identify and remove external dependencies in the use case layer of the application to enforce the Common Closure Principle (CCP) and know how to create instrumented tests on Android with mock data sources.

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete