Recommend use of MVP/MVVM/MVI patterns

futurice / android-best-practices

Do's and Don'ts for Android development, by Futurice developers

Other

20.35k stars 3.37k forks source link

Recommend use of MVP/MVVM/MVI patterns #150

Open peter-tackage opened 7 years ago

peter-tackage commented 7 years ago

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.

jflavio11 commented 6 years ago

Clean architecture should be the best option and, in my opinion, package structure by feature is not too scalable

peter-tackage commented 6 years ago

Clean architecture goes a bit beyond the presentation logic of MVP/MVVM/MVI, it's more of an overall app architecture. At the moment, I'd be tempted to be a little more opinionated and suggest Clean Architecture with MVVM/MVI as the presentation layer.

How would you recommend package structure in a way that was scalable? and what about a feature packaging is not scalable?

fuhoi commented 6 years ago

Long time reader and user of these Android best practice docs but first time commenter. I'm currently working on a project using a Clean variant with MVP and feature packages - it's working well for the current project use cases. It really helps to groups things together and allows our devs to communicate/move across platforms easily.