Background: I’m currently, for my University, creating some simple apps showcasing the possible educational potential of the Microsoft Surface. Their functionality falls somewhere between a basic demo app and a full-fledged production app.
Our hesitation with using MVVM or some other type of MVC is that, with the exception for the few apps that we have which are data-backed, most of our apps are deeply tied to their presentation (i.e. the Surface touchscreen). It doesn’t seem logical to emphasize such extreme separation of business logic and the view in this circumstance.
Any ideas?
I’ve used MVVM with great success with Surface. MVVM is about modeling your views and separating out whatever logic is behind them. It doesn’t matter whether that logic deals with databases or whatever. If you have a view, it is a view of something. Therefore that something should be represented by your view model.