-
make the code maintainable, readable by introducing mvp architecture
-
看了下您的框架, 发现约束类没有model层,为什么呢
-
业务在不断推进,团队的多人协作效果并不是很好,业务内容庞大且繁杂,不同成员迥异的实现风格使得项目的维护成本越来越高,是时候做一次架构上的重构了。
大致的目标如下:
- **易用性**
迁移的成本需要适当控制,不能给开发人员过重的额外代价,不然新架构根本推不动;可以考虑部分代码自动生成
- **可测试性**
将UI代码与业务代码进行拆分,UI层和业务层可以分别进行单元测试 #47
- *…
-
- The particular pattern being used is not as is the separation of concerns and testability.
- Encourage keeping Activities and Fragments thin/logic free.
- Reference Freesound app.
-
Where is the DaggerAppComponent file?
DaggerAppComponent.builder()
.application(this)
.build()
.inject(this)
-
[android开发规范_丰驰APP.zip](https://github.com/celonJ/materials/files/1244218/android._.APP.zip)
-
### Proposal for implementing the MVP architecture by [Google](https://github.com/googlesamples/android-architecture/tree/todo-mvp-rxjava) or [Ribot](https://github.com/ribot/android-boilerplate)
W…
-
Can't we refactor the Navigation responsibility from the presenters into separate class called Navigator that will be injected to the presenter.
So that we will have reusable navigation methods, like…
-
Address the very high cyclomatic complexity we are seeing from Codacy by breaking up Activities & Fragments according to one of the well-respected architectural patterns (MVP / MVVM / etc)
-
So when an application needs anything it will request that from DataManager. For a simple application with 8-15 API call, it is ok. But think when you have so many different services (Food, Ride, Mart…