理解android-architecture mvp

https://github.com/googlesamples/android-architecture

todo_mvp

A contract class which defines the connection between the view and the presenter.
An Activity which creates fragments and presenters.
A Fragment which implements the view interface.
A presenter which implements the presenter interface in the corresponding contract.

Presentation Layer

契约类Contract View和Presenter的联系
Activity中实例化Fragment和Presenter
创建Fragment中实现BaseView接口
创建Presenter并实现契约类中的Presenter接口

Data Layer

data ：该分包下主要是数据层的代码，即 MVP 中的 Model 层

接口TasksDataSource 规范操作数据的接口
类TasksRemoteDataSource 实现TasksDataSource 接口，实现真正操作数据的逻辑。
类TasksLocalDataSource 实现TasksDataSource 接口，实现真正操作数据的逻辑。
类TasksRepository 实现TasksDataSource接口，持有TasksRemoteDataSource mTasksLocalDataSource 对象。

todo-mvp-clean

It’s based on the MVP sample, adding a domain layer between the presentation layer and repositories, splitting the app in three layers:

MVP: Model View Presenter pattern from the base sample.
Domain: Holds all business logic. The domain layer starts with classes named use cases or interactors used by the application presenters. These use cases represent all the possible actions a developer can perform from the presentation layer.
Repository: Repository pattern from the base sample

增加了域层use cases 表示presentation layer的行为

Key concepts
The big difference with base MVP sample is the use of the Domain layer and use cases. Moving the domain layer from the presenters will help to avoid code repetition on presenters (e.g. Task filters).
Use cases define the operations that the app needs. This increases readability since the names of the classes make the purpose obvious (see tasks/domain/usecase/).
Use cases are good for operation reuse over our domain code. CompleteTask is a good example of this as it’s used from both the TaskDetailPresenter and the TasksPresenter.
The execution of these use cases is done in a background thread using the command pattern. The domain layer is completely decoupled from the Android SDK or other third party libraries.

将domain layer从 presenter分离，有利于减少 presenter的代码重复
Use cases提高代码的可读性
Use cases利用command模式，后台线程执行，和第三方库解耦