We will be using Kotlin Programming Language.

In this tutorial, we will learn MVP (Model-View-Presenter) in Android using Kotlin and We will implement Dependency Injection (DI) using Dagger2 Library, we will also implement Retrofit2 using Kotlin in our MVP Android project.

We will learn everything in the following sequence.

  1. We will learn about MVP Design Pattern.
  2. How to implement MVP in Android.
  3. Project folder structure for MVP in Android using Kotlin.
  4. MVP code sample in Kotlin.
  5. We will learn about Dependency Injection.
  6. Setup Gradle dependencies for Dagger2 and Retrofit in Android Studio for Dagger2.
  7. Implement Dagger2 (DI) in our sample MVP Android App sample project using Kotlin.
  8. Implementing Retrofit using Kotlin in our MVP Android sample project.

What is MVP Design Pattern?

Model View Presenter is an architectural pattern used to encourage/facilitate separation of concern in software projects.

MVP improves application architecture and facilitate unit testing.

MVP Architecture in Android separates business logic from view (activities/ fragments/custom views) through the presenter.

The Model:

Model layer is used to provide data to populate user interface.

Based on the business logic Model layer can provide required data from Network (through API call), from Application Shared Preferences or from SQLite Database

Model layer cannot directly communicate with View. Although it has to provide data to the View (UI) but it will do so through presenter layer.

The View:

Any Activity, Fragment, CustomView, Dialog or any other UI widget in our Android Application is considered as View.

View’s Responsibilities:
  1. Pass user interaction for example ( Button click event, touch interaction) to the presenter.
  2. The view has reference to the presenter so it will call any method in presenter based on any user interaction with the view (for example button click)
The Presenter:

The presenter is the middleman between View and Model.

Any user interaction with View is passed to Presenter, for example, a user Click on Login Button on Login Activity.

This action (login button click) is passed to the presenter. Now its presenter responsibility to validate login credentials (for example username and password).

Make Login API call and return its response to the View.

Presenter layer should not access Android API’s.

View has a reference to the Presenter.

mvp in android
MVP Android Diagram

To make sure we are implementing MVP in Android according to its ground rules:

Make sure you follow above MVP Android rules.

Let’s learn how to organize project file structure.

I have created following packages in my project.

MVP in Android packages
MVP Android packages structure

We will also add Base Activity Class, all activities in our project will implement Base Activity.

What will be inside Base Activity:

BaseActivity is an abstract class the basic purpose is to put all of code which is common in all activities over here. This avoids code reputation and also result in clean and precise code.

In our case our base activity is directly inherited from AppCompatActivity. Here we can see we are implementing IView interface(It will be explained later) in our BaseActivity. Below is code for BaseActivity.

abstract class BaseActivity : AppCompatActivity(),IView {

     * A dialog showing a progress indicator and an optional text message or
     * view.
    protected var mProgressDialog: ProgressDialog?=null

    override fun onCreate(savedInstanceState: Bundle?) {


    fun initialzeProgressDialoge(){

        if(mProgressDialog==null) {

            mProgressDialog = ProgressDialog(this)
            mProgressDialog!!.isIndeterminate = true


    override fun onPostCreate(savedInstanceState: Bundle?) {


    override fun onResume() {

    override fun onDestroy() {

    abstract fun setLayout():Int
    abstract fun init(savedInstanceState: Bundle?)
    abstract fun onStartScreen()
    abstract fun stopScreen()

    fun showProgress(msgResId: Int,
                     keyListener: DialogInterface.OnKeyListener?) {
        if (isFinishing)

        if (mProgressDialog!!.isShowing) {

        if (msgResId != 0) {

        if (keyListener != null) {

        } else {

     * @param isCancel
    fun setCancelableProgress(isCancel: Boolean) {
        if (mProgressDialog != null) {

     * cancel progress dialog.
    fun dismissProgress() {
        if (mProgressDialog != null && mProgressDialog!!.isShowing) {

    override fun hideLoading() {

    override fun showLoading() {
        showProgress(R.string.loading, null)

    override fun loadError(e: Throwable) {

    override fun loadError(msg: String) {

    Improper handling in real case

    protected fun showHttpError(e: Throwable) {

    override fun onStop() {


As We are following MVP Architectures, as We discussed each Activity class in our project will have Presenter.

Our All presenters will be inherited by base presenter

What will be inside Base Presenter:

In MVP memory leak is a very common issue which is caused mostly by network calls. Imagine a scenario where we send a network request and our activity get destroyed.

Now lets see what we have in our base presenter.

We are setting the view as volatile so we could use it among different threads. We have a method to add disposals into our composite disposal. We made a method to unbind view which cleans our composite disposal and also set our view to null so GC can clean it.

open class Preseneter<V>(@Volatile var view: V? ){

    companion object {

        var compositeDisposables: CompositeDisposable
        Every method which will be part of presenter lyer will be added in it so we could dispose off them once they are no more in our use
        var compositeDisposables: CompositeDisposable=CompositeDisposable()


    init {


    protected fun view(): V? {
        return view

    fun unbindView() {
        if (compositeDisposables != null) {
        this.view = null

    fun addDisposable(disposable: Disposable) {


MVP in Android using Kotlin Sample code Example:

We will create Login Activity which will be following MVP (Model-View-Presenter) in Android using Kotlin.

Login Activity will be inside ui Package.

mvp for Android using Kotlin
MVP Android Login Code
interface LoginPresenter {

    fun peformLogin(userName: String, userPassword: String)

    fun validateUser(userName: String, userPassword: String)
interface LoginView {

    fun navigateToHome()

    fun onBackPress()

    fun onPasswordError()
  // LoginActivity will implement LoginView Interface.

class LoginActivity : AppCompatActivity(), LoginView {

    lateinit var loginPresenter: LoginPresenter

    override fun onCreate(savedInstanceState: Bundle?) {

        // Initialize Presenter Implementation in onCreate.
        // And pass it reference to the View.
        // So Presenter can call View (LoginActivity) methods.

        loginPresenter = LoginPresenterImpl(this)
        loginPresenter.validateUser("hammad", "")


    override fun onPasswordError() {
        TODO("not implemented") //To change body of created functions use File | Settings | File Templates.

    override fun onBackPress() {
        TODO("not implemented") //To change body of created functions use File | Settings | File Templates.

    override fun navigateToHome() {
class LoginPresenterImpl(var loginViewInit: LoginView) : LoginPresenter {

    override fun validateUser(userName: String, userPassword: String) {
        // This function inside presenter layer
       // will have username and password validation logic.
      if (userPassword=="")

 override fun peformLogin(userName: String, userPassword: String) {
      if (userName == "hammad") {

We are done with learning Model View Presenter (MVP) in Android using Kotlin.

Now we will implement dependency injection using the Dagger2 framework and we will make API call inside performLogin() function of our presenter using Retrofit.

Now we are at Step5 of the Android MVP using Dagger2 and Retrofit in Kotlin Tutorial.

What is Dependency Injection (DI):

Dependency Injection (DI) is a design pattern in software engineering.

It is a mechanism of providing required dependencies to other objects.

For example, You have three classes in your project. ClassA, ClassB, ClassC.

ClassC needs an object of ClassA and ClassB.

Whereas ClassB needs an object of ClassA.

Android dependency injection with mvp
Dependency Injection Example

This means ClassC depends on ClassA and ClassB. And ClassB depends on ClassA. (One class is dependent on another class / Dependency).

Now we don’t want to create objects of ClassA and ClassB inside ClassC. We want to provide/pass initialized objects of ClassA and ClassB to ClassC.

For this purpose, we will inject (provide) required objects (dependencies) to ClassC.

We will use Dagger2 Library for this purpose.

What is Dagger2 Dependency Injection (DI)?

Dagger2 is a framework which is used to provide/manage dependencies. It uses annotations.

Annotations in Dagger2 (DI):

@Provides Annotation in Dagger2:

@Provides annotation in Dagger is used with methods which provide the certain dependency.

For example below function, provideRetrofit is annotated with @Provides annotation (which means it will provide a dependency of type Retrofit object).

Because below function return type is Retrofit, so Dagger2 will know that whenever it needs Retrofit object it will use this function.

// Retrofit object is available for dependency injection.

fun provideRetrofit(gson: Gson): Retrofit {
    return Retrofit.Builder().addConverterFactory(GsonConverterFactory.create(gson))

We add functions annotated with @Provides annotation inside Module Classes.

@Module Annotation in Dagger2:

Below NetModule class is annotated with @Module annotation and it can provide an object of type Retrofit, Gson, and INetworkAPI through @Provides annotated functions.

class NetModule {
    fun provideRetrofit(gson: Gson): Retrofit {
                return Retrofit.Builder()

    fun providesGson(): Gson {
        return GsonBuilder().create()

    // This function need Retrofit object which we are passing in argument.
    // We will not create Retrofit object in this function.
    // Instead it will be injected/provided by Dagger2.
    // Dagger2 will get Retrofit object from provideRetrofit function declared above.
    fun provideNetworkService(retrofit: Retrofit): INetworkApi {
        return retrofit.create(INetworkApi::class.java)

@Component Annotation in Dagger2:

// we already discussed NetModule class above.

@Component(modules = [NetModule::class])
interface ApplicationComponent {

     // this means ApplicationComponent has to provide/inject
     // required dependencies in LoginPresenterImpl class.

    fun inject(mLoginPresenterImpl: LoginPresenterImpl)

Now we are at Step6 of the tutorial.

Setup Gradle dependencies for Dagger2 and Retrofit in Android Studio for Dagger2.

Below is my module build.gradle file.

Don’t forget to add plugins and related dependencies.

apply plugin: 'com.android.application'

apply plugin: 'kotlin-android'
apply plugin: 'kotlin-kapt'
apply plugin: 'kotlin-android-extensions'

android {

    kapt {
        generateStubs = true
    compileSdkVersion 27
    defaultConfig {
        applicationId "com.es.developine"
        minSdkVersion 15
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"
    implementation 'com.android.support:appcompat-v7:27.1.1'
    implementation 'com.android.support.constraint:constraint-layout:1.1.0'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.1'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'

    implementation 'com.squareup.retrofit2:retrofit:2.4.0'
    implementation 'com.squareup.retrofit2:converter-gson:2.4.0'
    implementation 'com.squareup.retrofit2:adapter-rxjava2:2.4.0'
    implementation 'io.reactivex.rxjava2:rxandroid:2.0.1'

    //  Dagger2 required Gradle dependencies.

    implementation 'com.google.dagger:dagger-android:2.15'
    implementation 'com.google.dagger:dagger-android-support:2.15'

    // if you use the support libraries
    kapt 'com.google.dagger:dagger-android-processor:2.15'
    kapt 'com.google.dagger:dagger-compiler:2.15'

Implement Dagger2 (DI) in our sample MVP Android App project using Kotlin.

Remember in the start of the tutorial, we created di package in our project.

We will add Dependency Injection (Dagger) related work like components and modules in our di package.

Create two packages, Component, and Module inside di package.

Add Interface ApplicationComponent in component package.

@Component(modules = [NetModule::class])
interface ApplicationComponent {
    fun inject(mLoginPresenterImpl: LoginPresenterImpl)

Create NetModule class and add it to module package.

class NetModule {

    fun provideRetrofit(gson: Gson): Retrofit {
        return Retrofit.Builder().addConverterFactory(GsonConverterFactory.create(gson))

    fun providesGson(): Gson {
        return GsonBuilder().create()

    fun provideNetworkService(retrofit: Retrofit): INetworkApi {
        return retrofit.create(INetworkApi::class.java)

Now we have to initialize ApplicationComponent class which is responsible to provide requested dependencies.

We will initialize it in Application Class which extends Application.

open class ApplicationClass : Application() {

    public lateinit var applicationComponent: ApplicationComponent

    override fun onCreate() {

        // ApplicationComponent is our component interface.
        // NetModule is our Module class.

        applicationComponent = DaggerApplicationComponent.builder()


Also, don’t forget to declare this ApplicationClass in Manifest file.

At this step, you might get unable to resolve DaggerApplicationComponent error in Android Studio.

Simply build -> Re-Build your project and issue will be fixed.

You have to add Internet Permission as well.

Because we are about to add Retrofit2 API call using Kotlin in our sample MVP Android App.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"

    <uses-permission android:name="android.permission.INTERNET" />


        <activity android:name=".ui.login.LoginActivity">
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />


We are done with Dagger 2 along with MVP (Model-View-Presenter) in Android using Kotlin.

Implementing Retrofit using Kotlin in our MVP Android sample project:

We have already added Retrofit and Gson Gradle Dependencies.

We will hit this free API and get JSON Response.


  1. Create interface INetworkApi in network package.
  2. Create a new Class/File EndPoints in network package.


interface INetworkApi {

    fun getAllPosts(): Observable<List<PostData>>


object Endpoints {
    const val posts = "posts/"
showing json list recyclerview kotlin
I also created posts package.

updated DaggerApplicationComponent.kt

@Component(modules = [AppModule::class, NetModule::class])
interface ApplicationComponent {

    fun inject(mewApplication: ApplicationClass)
    fun inject(mLoginPresenterImpl: LoginPresenterImpl)
    fun inject(mLoginActivity: LoginActivity)
    fun inject(mPostPresenterImpl: PostPresenterImpl)


Data Class PostData.kt (List of Posts/ API Response Model Class)

data class PostData(
      @SerializedName("userId") val userId: Int,
      @SerializedName("id") val id: Int,
      @SerializedName("title") val title: String,
      @SerializedName("body") val body: String

Interface PostView.kt

interface PostView {

    fun showAllPosts(postList: List<PostData>)

If you have any confusion, a suggestion for improvement please let me know through the comments section.

Interface PostPresenter.kt

interface PostPresenter {

    fun getAllPosts()


class PostActivity : AppCompatActivity(), PostView {

    lateinit var postPresenter: PostPresenter

    override fun onCreate(savedInstanceState: Bundle?) {

        postPresenter = PostPresenterImpl(this, application)


    override fun showAllPosts(postList: List<PostData>) {

        Log.d("Response", "" + postList)


Class PostPresenterImpl.kt

class PostPresenterImpl(var postView: PostView, var applicationComponent: Application) : PostPresenter {

    lateinit var mNetworkApi: INetworkApi

    init {
        (applicationComponent as ApplicationClass).applicationComponent.inject(this)

    override fun getAllPosts() {

        var allPosts = mNetworkApi.getAllPosts()
                .subscribe {



Recommended Reading:

21 Responses

  1. Not make sense to me. Why you have to code a lot to click in a button, make some background work and go to next activity?
    MVP is waste of “code” in my opnion.

    1. Hi Lacroiix, it’s just not about button click. The basic purpose of any code architecture is to manage code in an efficient way. MVP in Android has three major parts.
      Presentation Layer – How to show data to the user.
      Data Layer – From where an application will get required data.
      Domain layer – what are main features of the application.
      Also, MVP in Android facilitate Unit testing. Views can be mocked to the presenter.
      Using MVP in Android views are independent of the data source.

      1. I’ve read about Clean Architecture by Antonio Cejas and he mentions the three layers or parts (Presentation, Data and Domain) but I’m a little confused. Do “Data” and “Domain Layers” belong to “Model”?

        1. If we look at the diagram of Clean Architecture by Cejas.
          He has mentioned that Data layer will provide data from Network through API call (Retrofit), Database (SQLite, Room) or memory (cache).
          Whereas Domain layer has Entities, Repositories, Model class. so in this way Domain layer and Model layer are same.

  2. what about validating multiple views…?
    how to set Error message to your multiple views using Presenter Implementation.?

        1. Atif as I thought, this work can be done inside presenter with required business logic, and when you need to show these views to UI then you can return back to View/Activity.

  3. hey i think mvp is about seperation of concerns means our view is responsible for ui events means any kind of validator should be applied on ui layer although business logic could be inside presenter layer as Noman said but validation must be provided on UI layer(as far as i think)

    1. Hi, Thank you 🙂
      Yes I think I should move views validation part to the view layer not to the presenter.
      Let me know if you can improve anything on its git repo for this android mvp kotlin example.

  4. Nice article on Android MVP using Kotlin.
    This article covers complete android app architecture as it includes dagger and retrofit also.
    and i can see retrofit2 is now following rx-android and rx-java approach.
    Can you please add example of handling error messages from presenter.
    As discussed in above comments.

  5. thankyou, everything about android mvp using Kotlin is explained well.
    but can you please prepare separate tutorial for retrofit api call using kotlin and displaying resulting json in recyclerview ?
    i shall be thankful.

  6. great article, well organized and cleared a lot of questions for me.
    One thing though, if not too much trouble, would you mind updating it using the AndroidInjectionModule that comes with dagger 2.11?

  7. thanks for awesome artical very helpfull …could you please explain BaseActivity in detailes

    1. You can define common behavior or utility functions inside Base Activity of your application.
      In addition to this, you can add abstract methods inside Base Activity and can override those method in different activities for different implementation.
      Also, you can define presenter for your Base Activity class to make presenter aware of activity life cycle if you are following MVP in Android.