Android App Architecture Patterns: The Why and How
Building an application is simple, but creating a maintainable, testable, and easily updatable app is challenging - this is why software developers get paid so much!
Object oriented programming (OOP) was developed as a solution to spaghetti code, and it has largely succeeded in addressing this issue. However, in modern complex applications, interdependencies between components can lead to tight coupling, resulting in spaghetti code.
An architecture design pattern focuses on structuring the interaction between components to achieve loose coupling, resulting in modular, reusable, and testable components. That is, a blueprint for enforcing single responsibility principle for components.
app components refer to the various elements that make up an application. They can include classes, functions, libraries, modules, or any other building blocks that are part of the application’s architecture.
Components must interact hence we need coupling, but coupling must be reduced to the nearest minimum to achieve loose coupling.
Tight coupling occurs when there is a strong dependency between different components. One example that illustrates the issue is the hierarchical relationship between classes. In this case, when a change is made in a parent class, it often necessitates corresponding modifications in the child classes. This cascade effect of changes ripples throughout the codebase, making it more challenging to maintain and increasing the risk of introducing errors.
Implementation
Implementing an architecture pattern may initially seem complex, but it enables future scalability of the app. Investing time and effort in the foundation development phase contributes to long-term project success. A solid foundation facilitates smoother development, enhanced maintainability, and scalability, ultimately saving time and effort in the future.
For example, Constructing a skyscraper necessitates the establishment of a sturdy structure that can support its substantial weight and meet specific needs. A flawed choice in the structure could lead to its collapse, hinder future development or pose safety risks.
All apps have User Interface and backend/business logic. Architecture patterns can help separate UI distinct from business logic and further separate business into manageable components (data repository and data manipulation)
While it’s possible to place all business logic within a UI (activity or fragment), as the app expands, it becomes harder to maintain.
For Android development, commonly used patterns include:
- MVVM(Model-View-ViewModel) : RECOMMENDED BY GOOGLE
- MVC (Model-View-Controller)
- MVP (Model-View-Presenter)
