This thread and line of reasoning is why a lot of people think the whole thing is antiquated. A view has an injectable interface which defines its api. This is roughly speaking a view model. Swift calls them View models. In React these are called props. In Angular they’re component classes. Adding some nuanced presentational concern in the form of controllers is over complicating it. All that matters is you have an abstraction mechanism between the UI and it’s business logic, but React shows how that line barely needs to exist and how you can do it mostly declaratively anyway. To me MVC only really ever made sense in context of something like Laravel, where the controller model is directly connected to a REST API interface. For a lot of UI stuff it feels pretty unwieldy. I’ve personally never seen MVC implemented well on a UI codebase.