A Better Architecture For iOS Apps: A Deep Look At The Model-View-Controller Pattern


If you’ve ever written an iOS app beyond a trivial “Hello world” app with just one screen and a few views, then you might have noticed that a lot of code seems to “naturally” go into view controllers.
Because view controllers in iOS carry many responsibilities and are closely related to the app screens, a lot of code ends up being written in them because it’s just easier and faster that way.
The post A Better Architecture For iOS Apps: A Deep Look At The Model-View-Controller Pattern appeared first on Smashing Magazine.
From our sponsors: A Better Architecture For iOS Apps: A Deep Look At The Model-View-Controller Pattern