Guide to Good Android App Architetture
Why Developers choose Poor Architetture Pattern?
Due to tight deadline developers choose to introduce quick-fixes and patches to the app. This can lead to accumulation of technical debts. Technical debt is the cost of future rework accumulated by avoiding work that should bave been done upfront. Technical debt is unavoidable as the scope of the project grows so it is always the best strategy to follow the best practices in app design and developement.
Some of the example of Poor App Development Practices are:
Testing and Building App only for specific device, without considering all the available devices in market. This can leads to comptalibility error and reduce app users to limited numbers.
Copy-Pasting third party code or implementing third party library can lead to unstability, unanticipated errors, conflicts and library compatibility issues.
Putting App’s business logic in Activity or Fragment can lead to large and unmanagable code.
