Nothing in an inner circle can know anything at all about something in an outer circle. …source code dependencies can only point inwards. In order to achieve this, we need to follow one simple but strict rule - the Dependency Rule, represented by those 3 arrows pointing to the center of the graph. The main purpose of this approach is a separation of concerns. This is where Clean Architecture comes in. We are still using it for our presentation layer but what we lacked was consistent architecture for other parts of our apps. MVP was our go to solution for a long time, for separating UI code from the rest of the app.Īfter Google released Architecture Components we’ve embraced their new guide to app architecture using the MVVM pattern and newly released components. I’m sure most developers have sooner or later tried using MVC, MVP or MVVM and found that one of those patterns suits their needs best - and we are no exception. There are a few well-known architectural patterns used in the Android community. Uncle Bob’s famous onion shaped representation of Clean Architecture
0 kommentar(er)
