You said you chose MVVM for this feature. When does MVVM actually hurt?
You answer that MVVM was enough to separate screen state into something testable and the team already knew it. It hurts with boilerplate on simple screens, state shared across several screens and complex flows, and bloated ViewModels.
ArchitectureShort answerAdvanced
You've been asked to move a 5-year-old MVC app (150 view controllers, almost no tests) to…
#mvvm #refactoring #strangler
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
ArchitectureShort answerBasics
This is a take-home review. You didn't use a single third-party library in the app you…
#trade-off