Blog

MVC design pattern divides an application into three major aspects: Model, View, and Controller. This process increases the size of view class among UI, data binding logic and business operations. To sum up, the MVC architecture pattern works towards making a code good code by reducing its size. It works on to make the codes easily manageable and cleaner.

1. Model

Model represent the data model and manage data status. also defines the business rules for data means as how the data can be changed and manipulated

2. view

View represent data at your layout and views and rendering UI, The View represents UI components like XML, HTML etc. Model and View interact with each other using the Observer pattern.

3. Controller

At a first glance, MVVM seems very similar to the MVP , because both of them do a great job in abstracting the view’s state and behavior. The Presentation Model abstracts a View independent from a specific user-interface platform, whereas the MVVM pattern was created to simplify the event driven programming of user interfaces.

The main players in the MVVM pattern are :

• The View — that informs the ViewModel about the user’s actions.
• The ViewModel — exposes streams of data relevant to the View.
• The DataModel — abstracts the data source. The ViewModel works with the DataModel to get and save the data.

The user interacts with a View. View calls the appropriate methods in the Presenter. The presenter updates a Model and modifies the View depending on the Model state. so now we solved the main issues we have faced in MVC now we can test and maintain and adding more features but we found new issue that we have a lot of interfaces this makes our code not reusable because every time you need to implement new features and want to use part of your code you will implement all of the overrides of methods at that interface, so MVVM solve this problem let’s see.

The advantages of MVP or any UI architectural patterns are :

• All components in the app can be tested easily and independently.
• Modification of app can be done without having to refactor entire app as there is a clear separation of code related to view and app logic.
• Developers can work on building components independently.