A Tale of Two Development Approach: Empirical Study on The Maintainability and Modularity of Android Mobile Application with Anti-Pattern and Model-View-Presenter Design Pattern

Software development on mobile devices is overgrowing. However, the software still frequently unstructured developed without any pattern that can facilitate other developers to continue that software development, we called this approach as "anti-pattern." To overcome the anti-pattern problem and with the goal of improving maintainability, the developer begins to apply various architectural design patterns such as MVC, MVP, and MVVM to the development of Android-based mobile application. In this paper, we compare maintainability and modularity between 2 applications build with design pattern (MVP) and without design pattern or commonly referred as 'anti-pattern' using jHawk 6 as a software metrics tools. Use of jHawk 6 reduced subjectivity of measurements in some of the previous studies that make this research more proven with the use of selected maintainability and modularity metrics from previous qualified studies. In the end, this study proved empirically, use of MVP Design pattern significantly increase modularity by two times. With this results, we strongly recommend the use of the MVP design pattern in android based mobile application development.