Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Liam Small](https://secure.gravatar.com/avatar/8c4ab918d7c6ec8346b247c59931ef0b?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
Liam Small
1,666 PointsModel View Controller in Swift
Okay, so I'm looking at the Model View Controller Design Pattern and I understand that an object assumes one of three roles.
But if, for instance, you create the views in code; instead of using interface builder or storyboard how does this work?
Because surely the UIViewController would need to initialise the views with frames etc so does this still mean it follows the MVC patten?
Any help would be great :)