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

1. Introduction to Clean Architecture

2. Android and Clean Architecture

3. Setting up a Multi-Module project

4. Setting up the Domain layer module

5. Creating the abstraction for our RxJava Observation Thread

6. Setting up the Business Data for the Domain Layer

7. Setting up the data access interface for the Domain Layer

8. Setting up the Domain Layer Interactor classes

9. Implementing the Get Projects use case

10. Implementing the get Bookmarked Projects use case

11. Implementing the Bookmark Project use case

12. Implementing the UnBookmark Project use case (Domain layer 8)

13. Testing the Get Projects use case

14. Testing the Get Bookmarked Projects use case

15. Testing the Bookmark Project use case

16. Testing the UnBookmark Project use case

17. Setting up the data module

18. Creating the data models for the data layer

19. Creating the external source interfaces for our data layer

20. Creating the data layer store interface

21. Creating the data layer cache data store

22. Creating the data layer remote data store

23. Creating the data store factory class

24. Creating the central access point for the data layer

25. Setting up the tests for the Data Layer

26. Testing the data store factory class

27. Testing the project entity mapper

28. Testing the projects data repository

29. Testing the projects cache data store

30. Testing the projects remote data store

31. Setting up the remote module

32. Creating the data models for the remote layer

33. Creating the Retrofit Service for the remote data source

34. Creating the Retrofit Service Factory for the remote service interface

35. Creating the data model mapper for the Remote Layer

36. Creating the Remote Source implementation

37. Setting up the Remote layer for testing

38. Testing the remote model mapper class

39. Testing the remote source implementation

40. Setting up the Cache module

41. Setting up the Cache layer data models

42. Creating the database for the cache layer

43. Creating the cached project Data Access Object

44. Creating the Configuration Data Access Object

45. Creating the cache model mapper

46. Creating the Projects Cache data source Implementation

47. Setting up the tests for our cache layer

48. Testing the cached project model mapper

49. Testing the Cached project DAO

50. Testing the Configuration DAO

51. Testing the projects cache implementation

52. Setting up the presentation module

53. Creating the data models for the presentation layer

54. Creating the data model mapper for the presentation layer

55. Creating the presentation state model

56. Creating the browse projects view model

57. Creating the bookmarked projects view model

58. Setting up the presentation module tests

59. Testing the view model mapper

60. Testing our Browse Projects View Model implementation

61. Testing our Browse Bookmarked Projects View Model implementation

62. Setting up the UI module

63. Creating the Post Execution Thread Implementation

64. Setting up the application class

65. Setting up the Dependency Injection for the UI module

66. Creating the UI modules Project representation

67. Creating the the Project model mapper for the UI module

68. Setting up the Browse Projects Activity

69. Configuring the DI for the project

70. Creating the Project item view

71. Creating the Browse Projects Adapter

72. Creating the browse bookmarked projects adapter

73. Creating the browse bookmarked projects activity

74. Tying together the browse projects and bookmarked projects activity

75. Setting up Unit Tests for the UI module

76. Test the project model mapper

77. Configuring the Dependency Injection for our User Interface tests

78. Writing Espresso tests for the Browse Projects Activity

79. Writing Espresso tests for the Bookmarked Projects Activity

80. Simplifying the work we have done