Don’t call it MVVM
Austin Feight
71

I think MVC pattern itself put a lot of pressure/burden on controller. So controller needs a separation layer which could do all the business logic modelings and controller could simply display them and perform other UI related changes. Honestly I feel controller could have 2 separate layers for model n network handling!