<story><title>iOS application architecture: MVVM, behaviors, singletons, subclassing</title><url>http://www.objc.io/issue-13</url></story><parent_chain></parent_chain><comment><author>mattgreenrocks</author><text>It is interesting that iOS apps suffer the same sort of runaway complexity that often plagues Rails apps, whereby the controller absorbs too much responsibility and becomes unmanageable. This is usually the collateral damage of an app growing within the overly tight conceptual confines of model&amp;#x2F;controller.&lt;p&gt;This points to a lack of developer education surrounding architecture and design. Most projects have too few abstractions, and&amp;#x2F;or a weak domain model. The Internet likes to complain about Java-style over-abstraction, but I&amp;#x27;ve never seen that.&lt;p&gt;I think devs don&amp;#x27;t like to think about architecture because it implies they&amp;#x27;re not doing things well, it is highly subjective, and they don&amp;#x27;t see the benefits immediately. All of these are poor reasons.</text></comment>
<story><title>iOS application architecture: MVVM, behaviors, singletons, subclassing</title><url>http://www.objc.io/issue-13</url></story><parent_chain></parent_chain><comment><author>kar-kub</author><text>I&amp;#x27;m very glad, as iOS developer, that community focus more and more on good iOS architecture. Few years back, in my impression, it was hard to find good article bout this topic, if any. 
I&amp;#x27;m really happy that objc.io is clearing that path with great developers willing to share theirs experience.</text></comment>