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.
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!
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?