Pure Model-View-Presenter in Android

It is quite complicated to find in the software development industry a standard in terms of architecture in Android development. It is true that, for some time, a very basic MVP has been proposed to break the God-Object (activities responsible for absolutely everything) and, since not so long ago, an MVVM proposed by Google, using its architecture components, is being adopted (ViewModel, LiveData, LifeCycleObserver…). Although these architectures (especially MVVM) fulfill the purpose of decoupling components and making them testable and reusable, we still find several points that make us ask ourselves if this is the best architecture we can use. In the first case, the view and the presenter are known, as well as the presenter and the model. Regarding the MVVM, although the ViewModel does not know the view, the view does know the ViewModel, which makes reusing views with different ViewModels complicated. The principle of investment of dependencies (DIP) is respected only in one direction (view = service, and not service = view).

✔ Read More...

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

mobile,android,mobile app development,mvvm,mvp