Thanks for sharing this, currently I use MVP, Don't get me wrong but it feels to me that mvvm was borned also from "the boilerplate that comes from MVP contracts", I saw some people criticizing that, without realizing that this is a problem from OOP languages itself besides than just an MVP problem. Another thing that worries me about MVVM is that all of the presentation code is moved into the view, and so, only testable via Espresso or Roboelectric, which makes me worry about moving into this patterns. What do you think about this two ideas?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for sharing this, currently I use MVP, Don't get me wrong but it feels to me that mvvm was borned also from "the boilerplate that comes from MVP contracts", I saw some people criticizing that, without realizing that this is a problem from OOP languages itself besides than just an MVP problem. Another thing that worries me about MVVM is that all of the presentation code is moved into the view, and so, only testable via Espresso or Roboelectric, which makes me worry about moving into this patterns. What do you think about this two ideas?