<?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: Tim Cook Gets Feisty</title>
	<atom:link href="http://www.mobilitysite.com/2009/01/tim-cook-gets-feisty/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mobilitysite.com/2009/01/tim-cook-gets-feisty/</link>
	<description>Mobile News, Reviews, and Views.</description>
	<lastBuildDate>Fri, 27 Nov 2009 17:20:21 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pony99CA</title>
		<link>http://www.mobilitysite.com/2009/01/tim-cook-gets-feisty/comment-page-1/#comment-14976</link>
		<dc:creator>Pony99CA</dc:creator>
		<pubDate>Fri, 23 Jan 2009 00:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/01/tim-cook-gets-feisty/#comment-14976</guid>
		<description>&lt;blockquote&gt;Software is the key ingredient, and we believe that we are years ahead of our competitors. Having different screen sizes, different input methods, and different hardware makes things difficult for developers.&lt;blockquote&gt;
So making things easier for developers is more important than pleasing customers?

Were Windows Mobile programs better when developers only had to support 240x320 portrait QVGA screens?  Yes, supporting the various resolutions makes software somewhat more difficult to write, but developers are smart people....

And, if an iPhone nano was basically just a shrunken iPhone, the developers wouldn&#039;t &lt;b&gt;have&lt;/b&gt; to do anything.  They &lt;b&gt;might&lt;/b&gt; want to lay out some items differently to make them more readable on a smaller screen, but allowing that to be configured by a user regardless of hardware is a good idea (for accessibility reasons).

&lt;blockquote&gt;Right now, from our point of view, the products in there are principally based on hardware that’s much less powerful than we think customers want, software technology that is not good, cramped keyboards, small displays.&lt;/blockquote&gt;
Cramped keyboards and small displays like, um, [cough]the iPhone[cough]?  Or is Apple saying there&#039;s really no middle ground between a laptop and a phone?

I suspect doogald has the right idea....

Steve&lt;/blockquote&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<blockquote><p>Software is the key ingredient, and we believe that we are years ahead of our competitors. Having different screen sizes, different input methods, and different hardware makes things difficult for developers.<br />
<blockquote>
So making things easier for developers is more important than pleasing customers?</p>
<p>Were Windows Mobile programs better when developers only had to support 240&#215;320 portrait QVGA screens?  Yes, supporting the various resolutions makes software somewhat more difficult to write, but developers are smart people&#8230;.</p>
<p>And, if an iPhone nano was basically just a shrunken iPhone, the developers wouldn&#8217;t <b>have</b> to do anything.  They <b>might</b> want to lay out some items differently to make them more readable on a smaller screen, but allowing that to be configured by a user regardless of hardware is a good idea (for accessibility reasons).</p>
<blockquote><p>Right now, from our point of view, the products in there are principally based on hardware that’s much less powerful than we think customers want, software technology that is not good, cramped keyboards, small displays.</p></blockquote>
<p>Cramped keyboards and small displays like, um, [cough]the iPhone[cough]?  Or is Apple saying there&#8217;s really no middle ground between a laptop and a phone?</p>
<p>I suspect doogald has the right idea&#8230;.</p>
<p>Steve</p></blockquote>
</blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: doogald</title>
		<link>http://www.mobilitysite.com/2009/01/tim-cook-gets-feisty/comment-page-1/#comment-14964</link>
		<dc:creator>doogald</dc:creator>
		<pubDate>Thu, 22 Jan 2009 16:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/01/tim-cook-gets-feisty/#comment-14964</guid>
		<description>I think the thing about lawsuits and Pre is not so much with its potential for success but with the fact that a former Apple executive who (I think) for a time managed the iPhone development, Jon Rubinstein, hired away a lot of his former employees at Apple who worked on the iPhone.

As for the Netbook, Apple&#039;s pooh-poohing sounds a lot like the pooh-poohing that they did for the three years that they were working on the iPhone. I am sure that they are working on something, but I agree with Apple - if they cannot get it priced competitively enough (i.e., less than $500), they may not do well in the category.

I thought another key quote was that Apple was interested in selling the best phone, not turning over the most units.</description>
		<content:encoded><![CDATA[<p>I think the thing about lawsuits and Pre is not so much with its potential for success but with the fact that a former Apple executive who (I think) for a time managed the iPhone development, Jon Rubinstein, hired away a lot of his former employees at Apple who worked on the iPhone.</p>
<p>As for the Netbook, Apple&#8217;s pooh-poohing sounds a lot like the pooh-poohing that they did for the three years that they were working on the iPhone. I am sure that they are working on something, but I agree with Apple &#8211; if they cannot get it priced competitively enough (i.e., less than $500), they may not do well in the category.</p>
<p>I thought another key quote was that Apple was interested in selling the best phone, not turning over the most units.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
