Yes, that's right.
In MVVM, the presentation model should be considered as a canonical source of data and user interface events (which leads to a number of important advantages, like better testability). You saved the printed NSString in the view model, and then bind it to the user interface.
With MVC, you have to use a controller or model instead, but the principle is the same: treat the view as temporary data and do important things elsewhere.
Justin spahr-summers
source share