MVVM stands for “Model View ViewModel”, and it’s a software architecture often used by Apple developers to replace MVC.
In MVC the way most Apple developers practice it, the view controller forms part of the Controller layer (the C in MVC), which means it’s responsible for doing lots of layout as well as being a general dumping ground for functionality.
In MVVM view controllers are considered part of the V layer, which means their job is to focus specifically on layout and the view lifecycle –
viewDidLoad() and so on. In its place a new object is created called the view model, which is effectively most of the code you had in your view controller before except without UIKit attached. That is, it should be capable of responding to requests for data, and so on, except it shouldn’t reference any user interface controls.
This might seem like you’re just pointlessly moving code around, but the difference is important: because your view model is more like a model than like a view you can write tests for it more easily. Rather than having to mock up a
UITextField to insert some data, you should be able to call a method that accepts a string because your view model shouldn’t rely on any user interface components.
While all this sounds positive, MVVM does have a big drawback on iOS: it relies on a system of two-way bindings that can communicate view data to your view model, otherwise you need to do a lot of work shuttling data around yourself.
Available from iOS – learn more in my book Swift Design Patterns
Did this solution work for you? Please pass it on!
Other people are reading…
About the Swift Knowledge Base
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Swift on the server is here
Get ahead of the game and learn server-side Swift with my latest book – build real-world projects while you learn!