This sample app has 2 screens. Packages are organized by feature:
- Looking up a list of Github repositories for a given username
- Getting more detail about a Github repository
Industry-standard Retrofit is used to query Github API and Dagger with custom scopes manages DI.
Below is the Model-View-Presenter setup:
Our Model is in the domain package.
The business logic is contained within GithubDataStore interface. RetrofitGithubDataStore is injected into Presenters via GithubDataStore from Domain layer interface. Presenters interact with Data layer only through Domain layer so the Data layer implementations can be easily swapped and to improve testability.
Conductor is used to manage Views. We have created a Base Controller View BaseViewController which extends Mosby's abstract MvpViewStateController. The Controller manages ViewState as well.
Instead of extending MvpViewStateController, the View could implement Mosby's MvpViewStateConductorDelegateCallback.
Our Presenters extend Mosby's MvpBasePresenter.
Instead of extending MvpBasePresenter, the Presenters could implement MvpPresenter.
Alternatively, the Presenters could extend Mosby's MvpNullObjectBasePresenter to avoid checks to see if the View is attached. However, this could result in some performance degradation as the this Presenter uses Reflection internally. This requires adding a new Gradle dependency com.hannesdorfmann.mosby3:mvp-nullobject-presenter.
Alternatively, the Presenters could extend Mosby's MvpQueuingBasePresenter to guarantee that the calls to View will be queued up and replayed if and when the View gets attached again. This requires adding a new Gradle dependency com.hannesdorfmann.mosby3:mvp-queueing-presenter.