Nice writeup on formalizing pattern names for approaches to avoiding that Massive View Controller problem it’s all too easy to slip into.
Massive View Controller
View controllers become gargantuan because they're doing too many things. Keyboard management, user input, data transformation, view allocation — which of these is really the purview of the view controller? Which should be delegated to other objects? In this post, we'll explore isolating each of these responsiblities into its own object. This will help us sequester bits of complex code, and make our code more readable.
Read more on khanlou.com