title: MVC design Pattern - Designing a Model
body: <p>I've been working with mvc design pattern to develop iOS, and I was wondering if I'm doing this right. I've read a lot about MVC, and, in my concept, all information that will be displayed or will change view's characteristics will be stored at the model (as it is the 'knowledge' of my vc). So, in my way designing MVCs, I usually create a mvc to each view that users interact, and I have model objects that manages all 'shared' information across the App, and one singleton to persist some data, the 'UserSession' class. For example:</p>
  
  <p>In my HomeViewController I have different subviews depending the status of my objects, so in this MVC (home) I have a 'presenter' as a model that controls my homeSubview type and their data. When I need to retrieve information from another model object (like user, or whatever object) is my 'presenter model' who do the trick (in this case), and the same happens in another mvc inside the project. My ways is something like: </p>
  
  <p>Controller [ask to] Model (that communicate with others model if needed) which ['respond' to] Controller then [update the] View</p>
  
  <p>So, that looks good to me, but I fell like I'm not using the mvc pattern correctly.  Can someone give a opinion?</p>
  
  <p>In advance: sorry about the english. And I appreciate any suggestion/help, Thank you!</p>