That's all they say MVP MVC MVVP for Android, what are they for?

I did not use this approach to programming, so I don’t understand why to do it all. They say that it simplifies the readability of the code. But still. You have to write code 10 times more.

What is the real advantage of this pattern? Maybe my thinking is a little different from yours. Just for me, let's say the Picasso library, simplifies the real life of a developer, it loads and installs a picture in 2-6 lines of code.

What this can give MVP MVC I do not understand .... Explain who the thread. Lost in Google

  • Do you write tests on your code? How big are your apps? - Mikhail Vaysman
  • one
    Google will not help, experience is needed here, and in real work, and if you are not working and not even in active search (work :)), you will remain in a lot of misunderstanding. - Rou1997

1 answer 1

At a minimum, you used the MVC approach (or MVVM, if you use data binding), if you managed to display something at all - this pattern is used by Android "by default" (xml markup - V, activity - C, then what is displayed (data) - M). The fact that you are not aware of which patterns you apply does not mean that they do not apply.

The advantages of MVVM and binding are evident at the slightest interest in this pattern. Other patterns are more “narrowly specialized” and the need to apply them comes from the tasks they solve, that is, if you don’t see (yet) the advantages of MVP, MVI or MVVM, then you don’t have them and you don’t need to think about it. When a problem appears, solutions will be required, understanding will come.