<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: iPhone Development for Beginners &#8211; 2010 Edition</title>
	<atom:link href="http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 05 Aug 2011 03:19:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Danilo Campos</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-5042</link>
		<dc:creator>Danilo Campos</dc:creator>
		<pubDate>Mon, 14 Feb 2011 20:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-5042</guid>
		<description>Not to be flip, but... I&#039;d start with a MacBook and go from there.</description>
		<content:encoded><![CDATA[<p>Not to be flip, but&#8230; I&#8217;d start with a MacBook and go from there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-5041</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 12 Jan 2011 17:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-5041</guid>
		<description>Any book suggestions for people wanting to develop on a PC?</description>
		<content:encoded><![CDATA[<p>Any book suggestions for people wanting to develop on a PC?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HomeGrown</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4704</link>
		<dc:creator>HomeGrown</dc:creator>
		<pubDate>Tue, 02 Mar 2010 01:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4704</guid>
		<description>Programming in Objective-C 2.0 by Kochan is a great book if you want to learn to program for the iPhone from scratch. You can also check out the Stanford CS193P lectures on iTunes U once you&#039;ve gone through the book.</description>
		<content:encoded><![CDATA[<p>Programming in Objective-C 2.0 by Kochan is a great book if you want to learn to program for the iPhone from scratch. You can also check out the Stanford CS193P lectures on iTunes U once you&#8217;ve gone through the book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zap Rowzdower</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4693</link>
		<dc:creator>Zap Rowzdower</dc:creator>
		<pubDate>Fri, 29 Jan 2010 01:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4693</guid>
		<description>Danilo. Hello Friend. I also would like to point out that you can learn Iphone SDK from the ground up at http://developer.apple.com/iphone/

What are your personal opinions of the Ipad? Will you start developing software for that? I think it&#039;ll be a big FLOP!

Zapster R.</description>
		<content:encoded><![CDATA[<p>Danilo. Hello Friend. I also would like to point out that you can learn Iphone SDK from the ground up at <a href="http://developer.apple.com/iphone/" rel="nofollow">http://developer.apple.com/iphone/</a></p>
<p>What are your personal opinions of the Ipad? Will you start developing software for that? I think it&#8217;ll be a big FLOP!</p>
<p>Zapster R.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danilo Campos</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4688</link>
		<dc:creator>Danilo Campos</dc:creator>
		<pubDate>Sat, 23 Jan 2010 22:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4688</guid>
		<description>Paul,

Don&#039;t love some of the other iPhone content I have from that publisher but the reviews for that book look great. I haven&#039;t read it so I can&#039;t endorse it either way. If you end up checking it out, let me know how it goes for you.

Good point on the iTunes U iPhone content. I don&#039;t love video lessons myself -- books work better for me -- but it&#039;s a good for someone who prefers classroom style instruction to get started once they have the basics of C and Objective-C.</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Don&#8217;t love some of the other iPhone content I have from that publisher but the reviews for that book look great. I haven&#8217;t read it so I can&#8217;t endorse it either way. If you end up checking it out, let me know how it goes for you.</p>
<p>Good point on the iTunes U iPhone content. I don&#8217;t love video lessons myself &#8212; books work better for me &#8212; but it&#8217;s a good for someone who prefers classroom style instruction to get started once they have the basics of C and Objective-C.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danilo Campos</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4687</link>
		<dc:creator>Danilo Campos</dc:creator>
		<pubDate>Sat, 23 Jan 2010 22:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4687</guid>
		<description>Brian,

Thanks for the comment. While Apple has an engineering team specifically dedicated to ensure ongoing compatibility on new versions of iPhone OS with older frameworks, that doesn&#039;t mean mean binaries compiled against those frameworks are guaranteed to be future proof. The problem is that when you trust someone else&#039;s code to stand between your work and the finished product, if something doesn&#039;t work quite right, you&#039;re either at the mercy of the community to fix it quickly or you&#039;ve got to sort out the fix yourself. Neither is an appealing proposition to me.

Moreover, when Apple releases a new SDK with new/enhanced APIs, anyone comfortable with previous versions can get to work with the new APIs immediately, instead of waiting around for someone else.

As for doing things that raise Apple&#039;s ire, dunno what to tell you. PhoneGap apps were being rejected for awhile. There&#039;s nothing unresearched about this -- &lt;a href=&quot;http://nachbaur.com/blog/phonegap-officially-permitted-on-the-app-store&quot; rel=&quot;nofollow&quot;&gt;here&#039;s a post on the subject&lt;/a&gt;. The FUD &lt;a href=&quot;http://twitter.com/brianleroux/status/8076342192&quot; rel=&quot;nofollow&quot;&gt;you complained about&lt;/a&gt; was created by Apple. I&#039;m glad to hear that Apple has changed their view of PhoneGap. But I&#039;m afraid Apple&#039;s overall opacity means that any tool that stands between the developer and Apple&#039;s officially-sanctioned methods of creating iPhone applications is a risk I can&#039;t encourage anyone to take. Apple may bless PhoneGap today. They may change their mind tomorrow. I truly hope that we&#039;re headed toward a more flexible and tolerant review process. Until that happens, though, it&#039;s worth minimizing risk.

Do I fear wasting a lot of development effort that gets rejected because Apple can be a control freak? Yup. Am I uncertain of Apple&#039;s overall view of such things? Of course, we all are. Do I doubt that it&#039;s a good idea to use anything but Apple-sanctioned tools? 100%, yes. Don&#039;t take this personally, though. I&#039;d say it about PhoneGap or anything else that wasn&#039;t the real deal. And that doesn&#039;t even get into the inherent compromises that come from writing an application that tries to be everything for every platform.

While I get that PhoneGap is meant to be a cross platform solution, it bills itself thusly:

&quot;If you’re a web developer who wants to build mobile applications in HTML and JavaScript while still taking advantage of the core features in the iPhone, Android, Palm, Symbian and Blackberry SDKs, PhoneGap is for you.&quot;

I read that as &quot;Hey, you web guys! Shortcut to mobile!&quot; Because I don&#039;t really concern myself with other mobile platforms at this stage, the fact that it can be a shortcut for other devices, too, is beside the point.

Look, your company wants to make money selling services around PhoneGap. I get that. Way to be out there protecting its reputation. But making something that works on every platform is a surefire ticket to mediocre software that doesn&#039;t look or work great on any platform. I think we can look to Java&#039;s resounding success on the desktop as proof of that fact. What&#039;s worse is that it&#039;s risky for iPhone developers in particular, given Apple&#039;s track record on &quot;not invented here&quot; intermediate code.

Glad we&#039;re in agreement, though, that using the official tools and APIs is the best way to build a great application.</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>Thanks for the comment. While Apple has an engineering team specifically dedicated to ensure ongoing compatibility on new versions of iPhone OS with older frameworks, that doesn&#8217;t mean mean binaries compiled against those frameworks are guaranteed to be future proof. The problem is that when you trust someone else&#8217;s code to stand between your work and the finished product, if something doesn&#8217;t work quite right, you&#8217;re either at the mercy of the community to fix it quickly or you&#8217;ve got to sort out the fix yourself. Neither is an appealing proposition to me.</p>
<p>Moreover, when Apple releases a new SDK with new/enhanced APIs, anyone comfortable with previous versions can get to work with the new APIs immediately, instead of waiting around for someone else.</p>
<p>As for doing things that raise Apple&#8217;s ire, dunno what to tell you. PhoneGap apps were being rejected for awhile. There&#8217;s nothing unresearched about this &#8212; <a href="http://nachbaur.com/blog/phonegap-officially-permitted-on-the-app-store" rel="nofollow">here&#8217;s a post on the subject</a>. The FUD <a href="http://twitter.com/brianleroux/status/8076342192" rel="nofollow">you complained about</a> was created by Apple. I&#8217;m glad to hear that Apple has changed their view of PhoneGap. But I&#8217;m afraid Apple&#8217;s overall opacity means that any tool that stands between the developer and Apple&#8217;s officially-sanctioned methods of creating iPhone applications is a risk I can&#8217;t encourage anyone to take. Apple may bless PhoneGap today. They may change their mind tomorrow. I truly hope that we&#8217;re headed toward a more flexible and tolerant review process. Until that happens, though, it&#8217;s worth minimizing risk.</p>
<p>Do I fear wasting a lot of development effort that gets rejected because Apple can be a control freak? Yup. Am I uncertain of Apple&#8217;s overall view of such things? Of course, we all are. Do I doubt that it&#8217;s a good idea to use anything but Apple-sanctioned tools? 100%, yes. Don&#8217;t take this personally, though. I&#8217;d say it about PhoneGap or anything else that wasn&#8217;t the real deal. And that doesn&#8217;t even get into the inherent compromises that come from writing an application that tries to be everything for every platform.</p>
<p>While I get that PhoneGap is meant to be a cross platform solution, it bills itself thusly:</p>
<p>&#8220;If you’re a web developer who wants to build mobile applications in HTML and JavaScript while still taking advantage of the core features in the iPhone, Android, Palm, Symbian and Blackberry SDKs, PhoneGap is for you.&#8221;</p>
<p>I read that as &#8220;Hey, you web guys! Shortcut to mobile!&#8221; Because I don&#8217;t really concern myself with other mobile platforms at this stage, the fact that it can be a shortcut for other devices, too, is beside the point.</p>
<p>Look, your company wants to make money selling services around PhoneGap. I get that. Way to be out there protecting its reputation. But making something that works on every platform is a surefire ticket to mediocre software that doesn&#8217;t look or work great on any platform. I think we can look to Java&#8217;s resounding success on the desktop as proof of that fact. What&#8217;s worse is that it&#8217;s risky for iPhone developers in particular, given Apple&#8217;s track record on &#8220;not invented here&#8221; intermediate code.</p>
<p>Glad we&#8217;re in agreement, though, that using the official tools and APIs is the best way to build a great application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trey Campbell</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4686</link>
		<dc:creator>Trey Campbell</dc:creator>
		<pubDate>Sat, 23 Jan 2010 16:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4686</guid>
		<description>Nice introduction/overview, Danilo.

Apress also has a deep discount on the eBook versions ($10) if you own the dead tree version. Like Roger said, I find it handy to be able to copy and paste code when I want to--worth $10 to me.

Also, highly recommend Dave and Jeff&#039;s books. I remember Dave&#039;s Mac Programming Primer books from eons ago.</description>
		<content:encoded><![CDATA[<p>Nice introduction/overview, Danilo.</p>
<p>Apress also has a deep discount on the eBook versions ($10) if you own the dead tree version. Like Roger said, I find it handy to be able to copy and paste code when I want to&#8211;worth $10 to me.</p>
<p>Also, highly recommend Dave and Jeff&#8217;s books. I remember Dave&#8217;s Mac Programming Primer books from eons ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian LeRoux</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4685</link>
		<dc:creator>Brian LeRoux</dc:creator>
		<pubDate>Fri, 22 Jan 2010 17:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4685</guid>
		<description>To be clear: PhoneGap is Apple approved as of 0.8.0, they reviewed the code and it only uses public api calls. And Apple will not be deprecating their own SDK anytime soon / it would eviscerate the (obviously wildly profitable) App Store marketplace.

The purpose of PhoneGap is to be a cross platform mobile solution for iPhone, Blackberry, Android, Symbian and Palm; not just an &#039;easier&#039; iPhone solution!

All that said, I agree, its great to learn the base programming languages to get the most out of the platforms they target.</description>
		<content:encoded><![CDATA[<p>To be clear: PhoneGap is Apple approved as of 0.8.0, they reviewed the code and it only uses public api calls. And Apple will not be deprecating their own SDK anytime soon / it would eviscerate the (obviously wildly profitable) App Store marketplace.</p>
<p>The purpose of PhoneGap is to be a cross platform mobile solution for iPhone, Blackberry, Android, Symbian and Palm; not just an &#8216;easier&#8217; iPhone solution!</p>
<p>All that said, I agree, its great to learn the base programming languages to get the most out of the platforms they target.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul_sns</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4683</link>
		<dc:creator>paul_sns</dc:creator>
		<pubDate>Fri, 22 Jan 2010 00:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4683</guid>
		<description>Nice walkthrough of iPhone development resources. I saw another book for &lt;a href=&quot;http://www.amazon.com/gp/product/0321566157?ie=UTF8&amp;tag=unlikely-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0321566157&quot; rel=&quot;nofollow&quot;&gt;Programming in Objective-C 2.0&lt;/a&gt; by Kochan in Amazon which had great reviews, would you also recommend that?

I would also like to suggest going to iTunes U and subscribing to the Stanford iPhone Applications Programming class. That&#039;s also one very useful resource indeed.

Thanks.</description>
		<content:encoded><![CDATA[<p>Nice walkthrough of iPhone development resources. I saw another book for <a href="http://www.amazon.com/gp/product/0321566157?ie=UTF8&amp;tag=unlikely-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0321566157" rel="nofollow">Programming in Objective-C 2.0</a> by Kochan in Amazon which had great reviews, would you also recommend that?</p>
<p>I would also like to suggest going to iTunes U and subscribing to the Stanford iPhone Applications Programming class. That&#8217;s also one very useful resource indeed.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danilo Campos</title>
		<link>http://blog.danilocampos.com/2010/01/20/iphone-development-for-beginners-2010-edition/comment-page-1/#comment-4682</link>
		<dc:creator>Danilo Campos</dc:creator>
		<pubDate>Thu, 21 Jan 2010 20:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danilocampos.com/?p=454#comment-4682</guid>
		<description>Good point, Roger. Forgot entirely to mention that. Yeah, you can definitely copy a block of code from a PDF eBook into Xcode.

On a first run-through, I find it more useful to hand-type whatever code is in an exercise. Afterward, if harvesting something useful to add to an existing project, being able to copy/paste is really handy.</description>
		<content:encoded><![CDATA[<p>Good point, Roger. Forgot entirely to mention that. Yeah, you can definitely copy a block of code from a PDF eBook into Xcode.</p>
<p>On a first run-through, I find it more useful to hand-type whatever code is in an exercise. Afterward, if harvesting something useful to add to an existing project, being able to copy/paste is really handy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

