Need help with CleanArchitectureManifest?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

ImangazalievM
445 Stars 38 Forks 67 Commits 0 Opened issues

Description

Description of the main principles and rules for building an Android application using Clean Architecture approach

Services available

!
?

Need anything else?

Contributors list

# 56,936
Kotlin
kotlin-...
Android
dagger2
58 commits
# 404,259
dagger2...
Android
rxjava-...
Kotlin
2 commits
# 404,740
Redux
Android
Kotlin
PHP
1 commit
# 469,195
dagger2...
Android
rxjava-...
Kotlin
1 commit
# 456,176
Java
dagger2...
Android
rxjava-...
1 commit

CleanArchitectureManifest

Clean Architecture Manifest (v. 0.9.5)

Here you will find description of the main principles and rules, that are worth following in developing Android apps using Clean Architecture approach.

Translations:

English | Русский

If you want to translate this document to your language, please visit this page.

Table of contents

Introduction

Clean Architecture is an approach suggested by Robert Martin in 2012.

Clean Architecture includes two main principles:

  1. Separation into layers
  2. Inversion of Control

Let's take a closer look at them.

1. Separating into layers

The main idea of this principle is separating whole app into layers. In general we have three layers:

  1. Presentation layer
  2. Domain layer (business logic)
  3. Data layer

2.Inversion of Control

According to this principle, domain layer must not depends on outer ones. That is, classes from outer layers must not be used in the domain layer. Interaction with outer layers is implemented through interfaces. Declaration of the interfaces contains in domain layer and their implementation contains in outer ones.

Thanks to separation of concerns between classes we can easily change an application code and add new functional with modifying minimal number of classes. In addition we get testable code. Please note that building the right app architecture depends entirely on a developer experience.

Advantages of Clean Architecture:

  • independent of UI, DB or frameworks
  • allows you to add new features faster
  • a higher percentage of test coverage
  • easy packages structure navigation

Disadvantages:

  • large number of classes
  • hard for beginners to understand

Attention: this article assumes knowledge on the following topics:

  • Dagger 2
  • RxJava 2

P. S. I developed an application to demonstrate the use of Clean Architecture in practice. You can find the source code here - Bubbble.

Find this article useful? ❤️

  • Support it by clicking the ⭐️ button on the upper right of this page. ✌️

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.