Daily iOS
Architecture

MVC vs MVVM

Someone proposes moving an app that works fine on MVC over to MVVM. What's the fundamental difference between MVVM and MVC?

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

MVVM pulls screen state and presentation logic into a ViewModel that doesn't depend on UIKit, and the View reflects that state through binding. Unlike MVC, where the Controller drove the View directly, dependencies run one way: View to ViewModel to Model.

Share a question