Building a View : Android GUI Architecture - Assembling a Graphical Interface - Wiring Up
the Controller - The Menu, Fragments and Multiplatform Support : Creating a Fragment -
Fragment Life Cycle - Fragment Manager - Fragment Transactions - The Compatibility
Package
MVC (Model View Controller) Architecture Pattern in Android with Example
Developing an android application by applying a software architecture pattern is
always preferred by the developers. An architecture pattern gives modularity to the project
files and assures that all the codes get covered in Unit testing. It makes the task easy for
developers to maintain the software and to expand the features of the application in the
future. There are some architectures that are very popular among developers and one of them
is the Model—View—Controller(MVC) Pattern.
The MVC pattern suggests splitting the code into 3 components. While creating the class/file
of the application, the developer must categorize it into one of the following three layers:
• Model: This component stores the application data. It has no knowledge about the
interface. The model is responsible for handling the domain logic(real-world business
rules) and communication with the database and network layers.
• View: It is the UI(User Interface) layer that holds components that are visible on the
screen. Moreover, it provides the visualization of the data stored in the Model and
offers interaction to the user.
• Controller: This component establishes the relationship between the View and
the Model. It contains the core application logic and gets informed of the user’s
behavior and updates the Model as per the need.
, In spite of applying MVC schema to give a modular design to the application, code
layers do depend on each other. In this pattern, View and Controller both depend upon
the Model. Multiple approaches are possible to apply the MVC pattern in the project:
• Approach 1: Activities and fragments can perform the role of Controller and are
responsible for updating the View.
• Approach 2: Use activity or fragments as views and controller while Model will be a
separate class that does not extend any Android class.
In MVC architecture, application data is updated by the controller and View gets the data.
Since the Model component is separated, it could be tested independently of the UI. Further,
if the View layer respects the single responsibility principle then their role is just to update
the Controller for every user event and just display data from the Model, without
implementing any business logic. In this case, UI tests should be enough to cover the
functionalities of the View.
Example of MVC Architecture
To understand the implementation of the MVC architecture pattern more clearly, here is a
simple example of an android application. This application will have 3 buttons and each one
of them displays the count that how many times the user has clicked that particular button.
To develop this application the code has been separated in the following manner:
• Controller and View will be handled by the Activity. Whenever the user clicks the
buttons, activity directs the Model to handle the further operations. The activity will
act as an observer.
the Controller - The Menu, Fragments and Multiplatform Support : Creating a Fragment -
Fragment Life Cycle - Fragment Manager - Fragment Transactions - The Compatibility
Package
MVC (Model View Controller) Architecture Pattern in Android with Example
Developing an android application by applying a software architecture pattern is
always preferred by the developers. An architecture pattern gives modularity to the project
files and assures that all the codes get covered in Unit testing. It makes the task easy for
developers to maintain the software and to expand the features of the application in the
future. There are some architectures that are very popular among developers and one of them
is the Model—View—Controller(MVC) Pattern.
The MVC pattern suggests splitting the code into 3 components. While creating the class/file
of the application, the developer must categorize it into one of the following three layers:
• Model: This component stores the application data. It has no knowledge about the
interface. The model is responsible for handling the domain logic(real-world business
rules) and communication with the database and network layers.
• View: It is the UI(User Interface) layer that holds components that are visible on the
screen. Moreover, it provides the visualization of the data stored in the Model and
offers interaction to the user.
• Controller: This component establishes the relationship between the View and
the Model. It contains the core application logic and gets informed of the user’s
behavior and updates the Model as per the need.
, In spite of applying MVC schema to give a modular design to the application, code
layers do depend on each other. In this pattern, View and Controller both depend upon
the Model. Multiple approaches are possible to apply the MVC pattern in the project:
• Approach 1: Activities and fragments can perform the role of Controller and are
responsible for updating the View.
• Approach 2: Use activity or fragments as views and controller while Model will be a
separate class that does not extend any Android class.
In MVC architecture, application data is updated by the controller and View gets the data.
Since the Model component is separated, it could be tested independently of the UI. Further,
if the View layer respects the single responsibility principle then their role is just to update
the Controller for every user event and just display data from the Model, without
implementing any business logic. In this case, UI tests should be enough to cover the
functionalities of the View.
Example of MVC Architecture
To understand the implementation of the MVC architecture pattern more clearly, here is a
simple example of an android application. This application will have 3 buttons and each one
of them displays the count that how many times the user has clicked that particular button.
To develop this application the code has been separated in the following manner:
• Controller and View will be handled by the Activity. Whenever the user clicks the
buttons, activity directs the Model to handle the further operations. The activity will
act as an observer.
