Are you using MVVM?

Question

Android

Question for experienced android developers. Do you use MVVM in real projects?
If yes, do you think it actually provides significant advantages over MVC?
The fact is that in my opinion:
1. By themselves, android projects without MVVM are already quite complex in structure and resemble Chinese noodles (some here, some there) and complicating them without good reason is doubtful.
2. MVVM exports part of the program logic to xml files. From experience in other areas of development, I know that this is bad. I have tools in that area for rendering logic into templates. Several years of using these tools led me to the conclusion - the logic should be concentrated in one place, and not spread out over templates.
3. With MVVM, entire classes are generated automatically, without the participation of a programmer. I also think that this is bad since the days of builders.
What do you think? How do you work in real projects?

Answer 1

I use Clean architecture with MVP in UI layer. In MVVM, I also did not like the lack of separation of responsibilities between elements.