Android Clean Architecture

Introduction to Clean Architecture

Autoplay

Up next

Android and Clean Architecture

About

So, you want to start using Clean Architecture in your Android projects? If so, it's important to get some of the basic concepts nailed down! In this lesson, we'll cover enough fundamental ideas of clean architecture so that we can start implementing the approach when it comes to developing mobile applications for Android.

Instructor

Links

Comments

Looks fantastic, i really hope this course is going to finally make me land to a job. Is covered everything, Please expect some questions:) Thank you guys from today Caster has an huge added value.

The architecture that you implement in this course, would it be considered MVVM as well?

Really IMPORTANT question - Why does some clean code articles have presentation depends on domain layer and the domain layer on the data layer. Whereas, your's is different? Your data layer has a dependency on the domain layer. You have the domain layer has the highest layer ( it doesn't depend on any layer ) ???

Hey there - great question!

The domain layer contains our application business logic, this means it has things such as models that define the core concepts of our project. Because of this, it should not depend on any other modules - this business logic does not (and should not) know about any other parts of the app. The approaches in those other places might not be as strict in implementing clean architecture or there may be other differences at play!

Hi Joe,

Thanks for the reply. The question is, and I'm sure, I'm sure, you must have seen this for yourself, in some representations, the Domain layer is intended as the middle layer which implements the Use Cases. The Data layer, in such case, is the one containing the entities, though the most inner layer.

This is where my confusion lies, and I'm trying to find a meaningful answer. What is your opinion on this?

regards

>

You need to go PRO to post comments.

Log In or Go Pro

Lessons in Android Clean Architecture

Introduction to Clean Architecture

Android and Clean Architecture

Setting up a Multi-Module project

Setting up the Domain layer module

Creating the abstraction for our RxJava Observation Thread

Setting up the Business Data for the Domain Layer

Setting up the data access interface for the Domain Layer

Setting up the Domain Layer Interactor classes

Implementing the Get Projects use case

Implementing the get Bookmarked Projects use case

Implementing the Bookmark Project use case

Implementing the UnBookmark Project use case (Domain layer 8)

Testing the Get Projects use case

Testing the Get Bookmarked Projects use case

Testing the Bookmark Project use case

Testing the UnBookmark Project use case

Setting up the data module

Creating the data models for the data layer

Creating the external source interfaces for our data layer

Creating the data layer store interface

Creating the data layer cache data store

Creating the data layer remote data store

Creating the data store factory class

Creating the central access point for the data layer

Setting up the tests for the Data Layer

Testing the data store factory class

Testing the project entity mapper

Testing the projects data repository

Testing the projects cache data store

Testing the projects remote data store

Setting up the remote module

Creating the data models for the remote layer

Creating the Retrofit Service for the remote data source

Creating the Retrofit Service Factory for the remote service interface

Creating the data model mapper for the Remote Layer

Creating the Remote Source implementation

Setting up the Remote layer for testing

Testing the remote model mapper class

Testing the remote source implementation

Setting up the Cache module

Setting up the Cache layer data models

Creating the database for the cache layer

Creating the cached project Data Access Object

Creating the Configuration Data Access Object

Creating the cache model mapper

Creating the Projects Cache data source Implementation

Setting up the tests for our cache layer

Testing the cached project model mapper

Testing the Cached project DAO

Testing the Configuration DAO

Testing the projects cache implementation

Setting up the presentation module

Creating the data models for the presentation layer

Creating the data model mapper for the presentation layer

Creating the presentation state model

Creating the browse projects view model

Creating the bookmarked projects view model

Setting up the presentation module tests

Testing the view model mapper

Testing our Browse Projects View Model implementation

Testing our Browse Bookmarked Projects View Model implementation

Setting up the UI module

Creating the Post Execution Thread Implementation

Setting up the application class

Setting up the Dependency Injection for the UI module

Creating the UI modules Project representation

Creating the the Project model mapper for the UI module

Setting up the Browse Projects Activity

Configuring the DI for the project

Creating the Project item view

Creating the Browse Projects Adapter

Creating the browse bookmarked projects adapter

Creating the browse bookmarked projects activity

Tying together the browse projects and bookmarked projects activity

Setting up Unit Tests for the UI module

Test the project model mapper

Configuring the Dependency Injection for our User Interface tests

Writing Espresso tests for the Browse Projects Activity

Writing Espresso tests for the Bookmarked Projects Activity

Simplifying the work we have done