This is a companion discussion topic for the original entry at https://www.raywenderlich.com/1941154-fundamental-ios-design-patterns/lessons/8
This is a companion discussion topic for the original entry at https://www.raywenderlich.com/1941154-fundamental-ios-design-patterns/lessons/8
Where does the idea that, in an MVC application, all objects must be a model, a view or a controller come from? I’ve never known that to be the case and am unaware of any other sources that assert it.
@jrg.developer Can you please help with this when you get a chance? Thank you - much appreciated! :]
Thanks for sharing the video here! That’s a nice talk too. 
For my perspective on this ––
The model-view-controller pattern separates objects into three main types: models, views and controllers –– Does this mean that your app won’t or can’t use other types? Nope.
However, the MVC pattern doesn’t directly focus on these types… it cares about whether something is a model, view or controller and how the interaction between them works.
This is called out at the end of the video as a shortcoming… as mentioned in your shared video, the question, “Is this a model, view or controller?” doesn’t actually make a lot of sense. Other objects do exist too –– the take of this video series (and related book) is that you should use other design patterns in combination with MVC to solve problems that MVC doesn’t (directly) address.