Member-only story
Building a high quality, maintainable and performant mobile app should be the goal of any serious developer. Following a recognizable and easy-to-follow design pattern is a great way to build your app from the ground up. We want to be able to revisit our codebase in 6 months and still feel confident that we can build upon or extend our apps if we need to. Additionally, we want to make it easier for new developers to join the team or project and be able to pick things up quickly.
As consultants, we also want to make sure that each time we deliver a codebase to a client, that it is easy to maintain, extend and augment in the future if necessary.
Architecture patterns are established designs and ways of structuring an application in order to minimize bugs, make code easier to read, understand, and test.
We’ll explore two of the most commonly used mobile app design patterns in this post, Model-View-Presenter and Model-View-ViewModel
Do not go around, we will go straight ahead main idea
1. MVP
Model:
The Model characterizes a set of classes to describe business logic. It also outlines the business rules for data on how data can be handled or changed.
View:
