I get the impression that MVVM only really works well when you have robust data-binding support baked into the framework (e.g. WPF&#x2F;XAML). Otherwise you end up with a bit of an impedance mismatch and a lot of overhead in keeping the views synced with the view model.<p>For example under iOS this probably means going all-in with ReactiveCocoa. But I&#x27;m not convinced that completely switching paradigms like that is the right way to go.