When you start learning coding to be a software developer, website developer, Android or iOS developer, your coding journey begins with simple programs for adding or subtracting two numbers, leap year, fibonacci series and then you move onto some small real world applications such as banking application with the three basic operations for balance enquiry, deposit and withdrawal.
Collecting user input, storing the input values in variables, defining methods/functions with proper validations and displaying the output, everything is covered in a single program.
However, desktop apps, web apps and mobile phone apps used by businesses are much more complex. Developing optimized apps easily is not possible without separating different layers of code. You cannot manage it if your code is not modular. It becomes difficult to update the app or add new features. This is the reason why you need an architecture for Android app development.
If you are a beginner, you should start with the MVP architecture.
MVP (model-view-presenter) is an architectural pattern that promotes separation of concerns and facilitates unit testing. This architecture has the following three components:
- Model (interactor, REST API, database API)
- View (activity, fragment, view)
It is the data store of the app. The model layer includes Shared Preferences, SQLite databases, and repositories for network calls. Model provides the data to be displayed in your app. API calls in the activity class are no longer needed. They are separated in the model and results can be retrieved from there.
It consists of fragments, activities and other views. The view is what you see on your screen. The data come from the presenter and populated into the views on the screen.
The presenter makes API calls, fetches data from files or databases, replaces fragments, fetches data from sharedpreferences, starts new activities and performs other similar tasks. The presenter contains the business logic.
The following are the features of MVP architecture:
- Separation of concerns
- Easier to debug
- Unit/integration testing
Now, let’s see the implementation of MVP architecture with an Android app using Dagger2, RxJava, GreenDao, PlaceHolderView, FastAndroidNetworking and AndroidDebugDatabase.
The app has the following packages:
- data package contains all the components that access and manipulate data.
- di package contains classes that provide dependency using Dagger2
- ui package contains view classes and corresponding presenters
- service package contains services for the app.
- utils package contains utility classes.
Classes in the app use key OOP features like inheritance and facilitate code reusability.
Library reference resources
Concept reference resources:
- Introduction to Dagger 2: Part 1
- Introduction to Dagger 2: Part 2
- Android Dagger2: Critical things to know before you implement
- The Best Android Networking Library for Fast and Easy Networking
- RxJava + Fast Android Networking
- Migrating from RxJava 1.0 to RxJava 2.0 and Learn RxJava by Examples
- Android Tinder Swipe View Example
- Debugging Android Databases And Shared Preferences In The Easiest Way
- RxJava Anatomy: What is RxJava, how RxJava is designed, and how RxJava works.
- Powerful Android ORM: greenDAO 3 Tutorial
When you are following architecture patterns like MVP, MVP clean or MVVM, this involves creation of basic files like API models, View, Presenter, and Android Activity and then boiler plate code. You have to spend 1-2 hours on each screen. You can use an automated template to save time and ease out work.
How to Install
Find and paste the MVPActivity folder under the root directory of android-mvp-architecture app at the below location:
C:\Program Files\Android\Android Studio\plugins\android\lib\templates\activities
Restart the Android Studio.
How to Use
Select the folder in which you want to create the new MVP folder. The following will be created in the new folder:
- View class