In an existing UIKit shopping app, the UIViewController handles the API calls, the cache, and the loading UI. When you move from MVC to MVVM, which layer would you put the networking and caching in?
Networking and caching go in a Repository layer wrapped in a protocol, not in the ViewModel, and the ViewModel's only job is turning the domain values the Repository returns into loading, success, and failure screen state.
ArchitectureShort answerAdvanced
You've been asked to move a 5-year-old MVC app (150 view controllers, almost no tests) to…
#mvvm #migration
ArchitectureShort answerAdvanced
This is a whiteboard design. You're building a stripped-down Outlook app with only a…
#repository #caching
ArchitectureShort answerBasics
Someone proposes moving an app that works fine on MVC over to MVVM. What's the…
#mvvm
ArchitectureMultiple choiceBasics
In MVVM, which of these should a ViewModel not have? Select all that apply.
#mvvm