A view model should read like a user interface specification. Most view models, however, are too busy raising property changed events or sending and subscribing to a message bus. This course will give you the tools and patterns you need to write clean, declarative code for WPF, Windows Phone, and Windows Store clients. A clean view model does one thing, and one thing only; the open source Assisticant library will handle the rest.
Mathematician and software developer, Michael L Perry applies formal proof to creating reliable software. He has developed a method starting from the works of the greats (Meyer, Rumbaugh, Knuth), and embodied it in his open-source frameworks (Update Controls and Correspondence).
Clean Mobile Apps Thank you for continuing this journey with me into Clean View Models with Assisticant. We've learned an awful lot about how to create clean view models and how the Assisticant library can help us to do that. Now we're going to learn a few techniques that will help us to create clean mobile apps that take advantage of the myriad devices. Mobile devices offer a unique set of challenges. They tend to be lower powered and need to respond quickly to the user's touch. But they also offer a unique set of capabilities such as location awareness, live tiles and toast notifications. But the availability of those capabilities differs as you go from one device to another. All of this conspires to make building mobile applications a unique challenge in software. This challenge is so unique you might like to have an Assisticant to help you and help you, she will with things like asynchronous operations, non-binding outputs, and background threads. Some of the ways in which we're required to write mobile code gets right down to the metal, but that doesn't mean that the code has to get dirty. I'll show you the patterns that you can use to keep your code clean and still rise to meet all of the challenges offered by mobile application development.