<story><title>How to Write Good iOS Apps</title><url>http://coffeetimerapp.com/index.php/2011/09/how-to-write-ios-apps/</url><text></text></story><parent_chain></parent_chain><comment><author>wallflower</author><text>The article was good in breadth but lacked depth.&lt;p&gt;For deep-dives into the nitty gritty of Cocoa Touch, we&apos;ve learned minute important details from digesting countless hours of WWDC videos that make all the difference.&lt;p&gt;&lt;a href=&quot;http://developer.apple.com/videos/wwdc/2011/&quot; rel=&quot;nofollow&quot;&gt;http://developer.apple.com/videos/wwdc/2011/&lt;/a&gt;&lt;p&gt;Especially the perennial classic, &quot;Designing Apps with Scrollviews&quot;</text></comment>
<story><title>How to Write Good iOS Apps</title><url>http://coffeetimerapp.com/index.php/2011/09/how-to-write-ios-apps/</url><text></text></story><parent_chain></parent_chain><comment><author>DrJokepu</author><text>&quot;Seriously, it&apos;ll be worth it not to learn about manual memory management.&quot;&lt;p&gt;This is not true at all and it is a very dangerous suggestion. Automatic Reference Counting indeed makes memory management an awful lot simpler (often you don&apos;t have to do any explicit memory management at all with it) but you still need to learn about it and understand it, otherwise all sorts of bad things will happen like memory leaks due to circular references (delegates come to mind) and crashes due to the autorelease pool high-water mark eating up all the memory on iOS devices.</text></comment>