You've been asked to move a 5-year-old MVC app (150 view controllers, almost no tests) to MVVM, and the service has to keep shipping. What's your strategy?
No big-bang rewrite. Put protocols on the boundaries (network, storage), protect with characterization tests, extract a ViewModel one screen at a time, and build new screens under the new rules. Keep a guide that allows both styles to coexist, and keep metrics.
ArchitectureShort answerAdvanced
You said you chose MVVM for this feature. When does MVVM actually hurt?
#mvvm #refactoring #strangler
ArchitectureShort answerAdvanced
You need to improve the structure of a massive ViewController in a live UIKit order…
#migration #legacy #refactoring
ArchitectureShort answerAdvanced
In an existing UIKit shopping app, the UIViewController handles the API calls, the cache…
#migration #mvvm
ConcurrencyShort answerAdvanced
You have an old networking layer built on completion handlers, called from hundreds of…
#migration #legacy