<?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 Realities Setting In</title>
	<atom:link href="http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/</link>
	<description></description>
	<pubDate>Thu, 08 Jan 2009 17:07:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sean P Aune</title>
		<link>http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/comment-page-1/#comment-13130</link>
		<dc:creator>Sean P Aune</dc:creator>
		<pubDate>Tue, 16 Jan 2007 06:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://seanpaune.com/?p=921#comment-13130</guid>
		<description>I'm not sure which way to lean on this.  Shari has a valid point in that Apple DOES have a track record of shafting early adopters (see:iPod), but Luis is right, it may just be a firmware upgrade.  It's hard to call at this point!</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure which way to lean on this.  Shari has a valid point in that Apple DOES have a track record of shafting early adopters (see:iPod), but Luis is right, it may just be a firmware upgrade.  It&#8217;s hard to call at this point!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/comment-page-1/#comment-13117</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Mon, 15 Jan 2007 15:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://seanpaune.com/?p=921#comment-13117</guid>
		<description>One possible reason: with all the leaks about the phone, Apple's stock would likely have plummeted without the announcement. 

You're also assuming that these features would be allowed by the FCC after further review. My point is that maybe it's more complicated than that. 

Not to mention that the features we're talking about are already built-in--the WiFi is there, the BlueTooth is there, even 3G features could be a software/firmeware upgrade away (like the WiFi-n on my new iMac). It's not a matter of the features being missing on the initial models as much as they are "turned off." They can be turned on after purchase--not to mention that in 6 months, a lot more could be developed and activated in the phones.

While it is a possibility, there is no evidence that Apple is intentionally hobbling the iPhone so as to shaft early adopters and sell more 2G and later models.</description>
		<content:encoded><![CDATA[<p>One possible reason: with all the leaks about the phone, Apple&#8217;s stock would likely have plummeted without the announcement. </p>
<p>You&#8217;re also assuming that these features would be allowed by the FCC after further review. My point is that maybe it&#8217;s more complicated than that. </p>
<p>Not to mention that the features we&#8217;re talking about are already built-in&#8211;the WiFi is there, the BlueTooth is there, even 3G features could be a software/firmeware upgrade away (like the WiFi-n on my new iMac). It&#8217;s not a matter of the features being missing on the initial models as much as they are &#8220;turned off.&#8221; They can be turned on after purchase&#8211;not to mention that in 6 months, a lot more could be developed and activated in the phones.</p>
<p>While it is a possibility, there is no evidence that Apple is intentionally hobbling the iPhone so as to shaft early adopters and sell more 2G and later models.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shari</title>
		<link>http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/comment-page-1/#comment-13078</link>
		<dc:creator>Shari</dc:creator>
		<pubDate>Mon, 15 Jan 2007 08:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://seanpaune.com/?p=921#comment-13078</guid>
		<description>I think one possibility is that Apple is trying to make sure that the early adopters will be buying another phone with more features in the near future. It may seem cynical but Apple has "taken advantage of (the users') love" in the past and wouldn't be beyond doing so again. 

If it was about regulations, they could have waited a bit longer and released a more functional phone. Why bother when all the Mac zealots will rush out and buy one then buy the next generation 8 months later?</description>
		<content:encoded><![CDATA[<p>I think one possibility is that Apple is trying to make sure that the early adopters will be buying another phone with more features in the near future. It may seem cynical but Apple has &#8220;taken advantage of (the users&#8217;) love&#8221; in the past and wouldn&#8217;t be beyond doing so again. </p>
<p>If it was about regulations, they could have waited a bit longer and released a more functional phone. Why bother when all the Mac zealots will rush out and buy one then buy the next generation 8 months later?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://www.seanpaune.com/2007/01/13/iphone-realities-setting-in/comment-page-1/#comment-13005</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Sun, 14 Jan 2007 17:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://seanpaune.com/?p=921#comment-13005</guid>
		<description>I have to wonder how many of the holdbacks are due to engineering and design, and how many are due to FCC restrictions or other non-technological considerations. I am struck by the iPhone's lack of use of these features despite having the technology and almost the exact same lack on the Zune. WiFi, but no networking; no downloading of songs directly from the portable; no wireless syncing with the computer; and so on.

Which begs the question: are the holdbacks technical, or are they jurisdictional? Which suggests that maybe, just maybe, the Japanese venue has fewer restrictions, and therefore the iPhone in Japan may have  different capabilities despite having the same specs.

While this won't help you get what you want in Missouri, it may help explain whyoy u're not getting what you want. I wonder if similar cell phone models between the U.S. and Japan have such differences in what features are locked or not.

It just seems unthinkable to me that Apple could build in all these technical capabilities and yet simply choose not to activate them. Microsoft did the same with the Zune, but with them, it was more likely a poor management choice. I can't see the same being possible with Apple, at least not to this degree.</description>
		<content:encoded><![CDATA[<p>I have to wonder how many of the holdbacks are due to engineering and design, and how many are due to FCC restrictions or other non-technological considerations. I am struck by the iPhone&#8217;s lack of use of these features despite having the technology and almost the exact same lack on the Zune. WiFi, but no networking; no downloading of songs directly from the portable; no wireless syncing with the computer; and so on.</p>
<p>Which begs the question: are the holdbacks technical, or are they jurisdictional? Which suggests that maybe, just maybe, the Japanese venue has fewer restrictions, and therefore the iPhone in Japan may have  different capabilities despite having the same specs.</p>
<p>While this won&#8217;t help you get what you want in Missouri, it may help explain whyoy u&#8217;re not getting what you want. I wonder if similar cell phone models between the U.S. and Japan have such differences in what features are locked or not.</p>
<p>It just seems unthinkable to me that Apple could build in all these technical capabilities and yet simply choose not to activate them. Microsoft did the same with the Zune, but with them, it was more likely a poor management choice. I can&#8217;t see the same being possible with Apple, at least not to this degree.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
