![]() ![]() The model layer is responsible for handing over the requested data to the ViewModel the ViewModel layer is responsible for processing the requested data into the business logic, and finally submitting it to the View layer for display, corresponding to the View one-to-one the View layer is only responsible for the interface drawing refresh, not processing the business logic Very suitable for distributing independent module development. MVVM development mode, low coupling, logically distinct. You only need to write the business logic of the project, no need to care about the network request, permission application, view life cycle and so on. Github source code: to fork, welcome star! Framework process Say goodbye to findViewById(), say goodbye to setText(), say goodbye to setOnClickListener(). MVVMHabit is an addictive and practical one based on Google's databinding, integrating popular libraries such as Okhttp+RxJava+Retrofit+Glide, and various native controls to customize BindingAdapter to make events and data sources perfectly bound. MVVMHabitĪt present, there are many development frameworks for android popular MVC and MVP modes, but there is very little development framework based on MVVM mode. ![]() ![]() Use this framework to quickly develop an Android app. Based on the DataBinding framework, a set of rapid development libraries for the MVVM design pattern integrates mainstream libraries such as Okhttp+RxJava+Retrofit+Glide to meet daily development needs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |