<?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: 10 New Year&#8217;s Resolutions for the iPhone</title>
	<atom:link href="http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/</link>
	<description>Straight Up Mobile Stuff.</description>
	<lastBuildDate>Wed, 30 Sep 2009 04:32:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Christina</title>
		<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/comment-page-1/#comment-47</link>
		<dc:creator>Christina</dc:creator>
		<pubDate>Thu, 22 Jan 2009 16:24:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.skratchboard.com/?p=203#comment-47</guid>
		<description>What a good idea! good work!</description>
		<content:encoded><![CDATA[<p>What a good idea! good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/comment-page-1/#comment-46</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 22 Jan 2009 07:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.skratchboard.com/?p=203#comment-46</guid>
		<description>Hi  iamnoskcaj,

Thanks for your comments. I respect your opinion, but there is no need to be rude about it. The list is a &quot;wish list&quot; and we realize some of these things maybe way off or may never happen. Doesn&#039;t stop us from dreaming does it?

In response to your specific comments:

1. It is generally a well-known fact that if you keep the piece of software running constant and increase the memory and processing power of the CPU, the system will run faster. You can consult anyone who has picked up a CS book.
2. We would encourage you to try using a device like the Nokia E71 a few days and see for yourself. Yes, it has 3G, GPS and does audio/video playback.
3. We think for the next little while, there will always be some performance difference between cameras on phones and point-and-shoot cameras. When 5MP+ becomes standard on camera phones, point-and-shoot will approach 10MP+ (for example). Our point is that we just want the iPhone to have a better camera for the times when we don&#039;t have our digicam around. 5MP+ cameras already exists on many Nokia phones. Check your Nokia catalog.
4. 720p is not necessary? Is Blu-ray necessary? Consumers continue to demand higher and higher performance/quality in their devices. You can argue that 5MP or 3MP cameras are not necessary too. If you haven&#039;t seen the Flip (http://www.theflip.com), go check it out. It&#039;s a tiny cheap video camera that does 720p.
5. I am glad you said you *personally* does not like Flash. The rest of us do :) Like it or not, a lot of websites are built using Flash. Without Flash support, it&#039;s difficult to deliver on the full promise of the web.
6. WiMax or LTE will come for mobile devices sooner or later. We agree that it probably won&#039;t happen this year. You are wrong though, that you need to have nationwide rollout before the device will support it. Devices will have both traditional radios too.
7. Point taken on this one. But instead of just not allowing this, we think AT&amp;T and Apple should work together on a solution.
8. You are right that it probably won&#039;t happen, but it&#039;s just our wish! Hard keyboards are still way more easier to type to many people.
9. No, we don&#039;t think we are there yet, but it will happen. OLED displays are real already for mobile phones. Foldable ones aren&#039;t that far away. Not WAY down the road.
10. You are absolutely wrong on this one. It&#039;s not the hardware vendors that they need to work with. It&#039;s the geospatial data providers like Tele Atlas and Navteq. But Apple can also license navigation engines from companies like ALK Technologies. They already have a solution for the iPhone (http://www.navigadget.com/index.php/2009/01/09/copilot-live-works-on-iphone).

Cheers,
James</description>
		<content:encoded><![CDATA[<p>Hi  iamnoskcaj,</p>
<p>Thanks for your comments. I respect your opinion, but there is no need to be rude about it. The list is a &#8220;wish list&#8221; and we realize some of these things maybe way off or may never happen. Doesn&#8217;t stop us from dreaming does it?</p>
<p>In response to your specific comments:</p>
<p>1. It is generally a well-known fact that if you keep the piece of software running constant and increase the memory and processing power of the CPU, the system will run faster. You can consult anyone who has picked up a CS book.<br />
2. We would encourage you to try using a device like the Nokia E71 a few days and see for yourself. Yes, it has 3G, GPS and does audio/video playback.<br />
3. We think for the next little while, there will always be some performance difference between cameras on phones and point-and-shoot cameras. When 5MP+ becomes standard on camera phones, point-and-shoot will approach 10MP+ (for example). Our point is that we just want the iPhone to have a better camera for the times when we don&#8217;t have our digicam around. 5MP+ cameras already exists on many Nokia phones. Check your Nokia catalog.<br />
4. 720p is not necessary? Is Blu-ray necessary? Consumers continue to demand higher and higher performance/quality in their devices. You can argue that 5MP or 3MP cameras are not necessary too. If you haven&#8217;t seen the Flip (<a href="http://www.theflip.com" rel="nofollow">http://www.theflip.com</a>), go check it out. It&#8217;s a tiny cheap video camera that does 720p.<br />
5. I am glad you said you *personally* does not like Flash. The rest of us do <img src='http://www.skratchboard.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Like it or not, a lot of websites are built using Flash. Without Flash support, it&#8217;s difficult to deliver on the full promise of the web.<br />
6. WiMax or LTE will come for mobile devices sooner or later. We agree that it probably won&#8217;t happen this year. You are wrong though, that you need to have nationwide rollout before the device will support it. Devices will have both traditional radios too.<br />
7. Point taken on this one. But instead of just not allowing this, we think AT&#038;T and Apple should work together on a solution.<br />
8. You are right that it probably won&#8217;t happen, but it&#8217;s just our wish! Hard keyboards are still way more easier to type to many people.<br />
9. No, we don&#8217;t think we are there yet, but it will happen. OLED displays are real already for mobile phones. Foldable ones aren&#8217;t that far away. Not WAY down the road.<br />
10. You are absolutely wrong on this one. It&#8217;s not the hardware vendors that they need to work with. It&#8217;s the geospatial data providers like Tele Atlas and Navteq. But Apple can also license navigation engines from companies like ALK Technologies. They already have a solution for the iPhone (<a href="http://www.navigadget.com/index.php/2009/01/09/copilot-live-works-on-iphone" rel="nofollow">http://www.navigadget.com/index.php/2009/01/09/copilot-live-works-on-iphone</a>).</p>
<p>Cheers,<br />
James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iamnoskcaj</title>
		<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/comment-page-1/#comment-42</link>
		<dc:creator>iamnoskcaj</dc:creator>
		<pubDate>Wed, 21 Jan 2009 17:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.skratchboard.com/?p=203#comment-42</guid>
		<description>This is a poorly prepared list -- clearly not thought out very well.  If any of this EVER happened, it certainly wouldn&#039;t happen in 2009.  

1.  What metrics do you have that supports this argument?  You have no earthly idea whether a &quot;faster processor and more memory&quot; would have ANY impact on the generalized problems you briefly mentioned.

2.  Show me a smart phone that uses 3G, GPS, and does audio/video playback that has 5 days of normal usage without a charge -- all with a MASSIVE, bright, LCD touch screen.  That&#039;s just not possible.  No smart phone goes 5 days without a charge, unless you&#039;re just not using it.

3.  As much as I&#039;d like a &quot;better&quot; camera, I don&#039;t think phones are quite ready to completely replace point and shoots.  How about a flash -- or some way to provide more consistent lighting.  There&#039;s no point in jacking up the megapixels if the picture it still going to be dark, blurry, or otherwise crappy.

4.  Clearly you know NOTHING about video -- 720P recording is just not necessary on a phone right now.  I&#039;m sure some manufacturers can cram it into a phone, but it&#039;s WAY too much for a small phone which isn&#039;t intended to be an HD Video Recording device.

5.  While It&#039;s unfortunate that Flash isn&#039;t supported, I&#039;m glad.  I personally don&#039;t like it, and I could just imagine how awful it would dog out a portable device.  As it is, simple DOM manipulation and CSS/Javascript effects are slow as hell in mobile browsers.  Flash would be even worse.  I think we should concentrate on having a rock solid browser that properly renders XHTML/CSS like a desktop -- but can display sites that are better geared towards mobile screens / interfaces.

6.  WiMax?  Seriously?  And how much do you know about WiMax?  I&#039;m sooo tired of hearing morons preach about the benefits of WiMax.  We would need to see MASSIVE WiMax network roll-outs (Nationwide) before someone like Apple would ever consider putting it in their handset.  While they&#039;re an incredible device and software company -- they seem to be targeting the masses with their device -- so I don&#039;t think they&#039;ll be putting something as new and experimental as WiMax in their device anytime soon.  Leave that to other, broader-reaching companies to experiment with first -- and when it&#039;s nice and ready, Apple will swoop in and take advantage of it.  If you listen to Steve Jobs&#039; original plans for cell phones -- his whole take on it was simple:  Everyone has a cell phone -- so if they could make a &quot;better one&quot; that the majority of people would use, then they&#039;d have a huge target market.  Focusing on bleeding edge tech like WiMax is NOT what they&#039;re trying to do right now.

7.  This is NOT Apple&#039;s fault.  It&#039;s an AT&amp;T thing.  They want to be able to CHARGE for this feature -- and as you can see -- if an App maker can make the phone do it for no additional cost, then AT&amp;T *thinks* they&#039;re losing potential revenue.  A card or usb dongle is easily $50/month -- and it uses WAY more bandwidth than a typical iPhone user would -- so they want to maximize their revenue.  Unfortunately it&#039;s not very uncommon -- but I wouldn&#039;t blame Apple.  I&#039;m sure their contract with AT&amp;T gave them little choice but to take down the app (AT&amp;T probably requested it).

8.  I don&#039;t see this happening anytime soon.  Apple was so proud of their software based keyboard ... and more so, I don&#039;t see them making TWO different iPhones.  When they make a decision about something like this (I compare it to the &quot;Two Button&quot; mouse issue that raged for 10-20 years) they tend to stick to their guns for as long as possible.  Heck, even after they caved in and made the Mighty Mouse -- it still doesn&#039;t have two VISIBLE buttons.  I think it&#039;s hilarious... but I don&#039;t think they&#039;ll change it because they&#039;d have to make two different models.  Maybe if they make a completely different version -- totally different design -- but I&#039;m not sold on the chance.

9.  Seriously?  A foldable OLED screen?  Do you really think we&#039;re &quot;there yet&quot; ??  Sure the proof of concept has been demonstrated -- but it&#039;s not mainstream enough -- and it&#039;s surely not something that could be mass-produced, cheaply -- and besides, I&#039;m not convinced that Apple wants a folding / flippable phone.  Maybe someday WAY down the road -- but not likely.

10.  No one currently does this.  To do it, there would need to be a DIRECT relationship with a current Turn By Turn hardware vendor. There&#039;s no way it will happen any other way.  That kind of access to GPS information has to be licensed.  Case in point:  Even though Google has &quot;directions&quot; -- it clearly states in their license that it&#039;s not supposed to be used for turn-by-turn directions while driving (even though people do it).   So for Apple to do it, they&#039;d need a license for the data, and I&#039;m guessing for many other reasons (insurance, etc) they&#039;d need to make some big design decisions.  What happens when a call comes in?  Do you remove it from the device holding it on your dash?  What about states that have &quot;hands-free&quot; laws?  You&#039;d be holding / using your phone while you&#039;re driving?  As much as I&#039;d like to see it happen -- I think it&#039;s going to take some big steps / changes to make it work.</description>
		<content:encoded><![CDATA[<p>This is a poorly prepared list &#8212; clearly not thought out very well.  If any of this EVER happened, it certainly wouldn&#8217;t happen in 2009.  </p>
<p>1.  What metrics do you have that supports this argument?  You have no earthly idea whether a &#8220;faster processor and more memory&#8221; would have ANY impact on the generalized problems you briefly mentioned.</p>
<p>2.  Show me a smart phone that uses 3G, GPS, and does audio/video playback that has 5 days of normal usage without a charge &#8212; all with a MASSIVE, bright, LCD touch screen.  That&#8217;s just not possible.  No smart phone goes 5 days without a charge, unless you&#8217;re just not using it.</p>
<p>3.  As much as I&#8217;d like a &#8220;better&#8221; camera, I don&#8217;t think phones are quite ready to completely replace point and shoots.  How about a flash &#8212; or some way to provide more consistent lighting.  There&#8217;s no point in jacking up the megapixels if the picture it still going to be dark, blurry, or otherwise crappy.</p>
<p>4.  Clearly you know NOTHING about video &#8212; 720P recording is just not necessary on a phone right now.  I&#8217;m sure some manufacturers can cram it into a phone, but it&#8217;s WAY too much for a small phone which isn&#8217;t intended to be an HD Video Recording device.</p>
<p>5.  While It&#8217;s unfortunate that Flash isn&#8217;t supported, I&#8217;m glad.  I personally don&#8217;t like it, and I could just imagine how awful it would dog out a portable device.  As it is, simple DOM manipulation and CSS/Javascript effects are slow as hell in mobile browsers.  Flash would be even worse.  I think we should concentrate on having a rock solid browser that properly renders XHTML/CSS like a desktop &#8212; but can display sites that are better geared towards mobile screens / interfaces.</p>
<p>6.  WiMax?  Seriously?  And how much do you know about WiMax?  I&#8217;m sooo tired of hearing morons preach about the benefits of WiMax.  We would need to see MASSIVE WiMax network roll-outs (Nationwide) before someone like Apple would ever consider putting it in their handset.  While they&#8217;re an incredible device and software company &#8212; they seem to be targeting the masses with their device &#8212; so I don&#8217;t think they&#8217;ll be putting something as new and experimental as WiMax in their device anytime soon.  Leave that to other, broader-reaching companies to experiment with first &#8212; and when it&#8217;s nice and ready, Apple will swoop in and take advantage of it.  If you listen to Steve Jobs&#8217; original plans for cell phones &#8212; his whole take on it was simple:  Everyone has a cell phone &#8212; so if they could make a &#8220;better one&#8221; that the majority of people would use, then they&#8217;d have a huge target market.  Focusing on bleeding edge tech like WiMax is NOT what they&#8217;re trying to do right now.</p>
<p>7.  This is NOT Apple&#8217;s fault.  It&#8217;s an AT&amp;T thing.  They want to be able to CHARGE for this feature &#8212; and as you can see &#8212; if an App maker can make the phone do it for no additional cost, then AT&amp;T *thinks* they&#8217;re losing potential revenue.  A card or usb dongle is easily $50/month &#8212; and it uses WAY more bandwidth than a typical iPhone user would &#8212; so they want to maximize their revenue.  Unfortunately it&#8217;s not very uncommon &#8212; but I wouldn&#8217;t blame Apple.  I&#8217;m sure their contract with AT&amp;T gave them little choice but to take down the app (AT&amp;T probably requested it).</p>
<p>8.  I don&#8217;t see this happening anytime soon.  Apple was so proud of their software based keyboard &#8230; and more so, I don&#8217;t see them making TWO different iPhones.  When they make a decision about something like this (I compare it to the &#8220;Two Button&#8221; mouse issue that raged for 10-20 years) they tend to stick to their guns for as long as possible.  Heck, even after they caved in and made the Mighty Mouse &#8212; it still doesn&#8217;t have two VISIBLE buttons.  I think it&#8217;s hilarious&#8230; but I don&#8217;t think they&#8217;ll change it because they&#8217;d have to make two different models.  Maybe if they make a completely different version &#8212; totally different design &#8212; but I&#8217;m not sold on the chance.</p>
<p>9.  Seriously?  A foldable OLED screen?  Do you really think we&#8217;re &#8220;there yet&#8221; ??  Sure the proof of concept has been demonstrated &#8212; but it&#8217;s not mainstream enough &#8212; and it&#8217;s surely not something that could be mass-produced, cheaply &#8212; and besides, I&#8217;m not convinced that Apple wants a folding / flippable phone.  Maybe someday WAY down the road &#8212; but not likely.</p>
<p>10.  No one currently does this.  To do it, there would need to be a DIRECT relationship with a current Turn By Turn hardware vendor. There&#8217;s no way it will happen any other way.  That kind of access to GPS information has to be licensed.  Case in point:  Even though Google has &#8220;directions&#8221; &#8212; it clearly states in their license that it&#8217;s not supposed to be used for turn-by-turn directions while driving (even though people do it).   So for Apple to do it, they&#8217;d need a license for the data, and I&#8217;m guessing for many other reasons (insurance, etc) they&#8217;d need to make some big design decisions.  What happens when a call comes in?  Do you remove it from the device holding it on your dash?  What about states that have &#8220;hands-free&#8221; laws?  You&#8217;d be holding / using your phone while you&#8217;re driving?  As much as I&#8217;d like to see it happen &#8212; I think it&#8217;s going to take some big steps / changes to make it work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Soulla</title>
		<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/comment-page-1/#comment-18</link>
		<dc:creator>Soulla</dc:creator>
		<pubDate>Tue, 06 Jan 2009 17:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.skratchboard.com/?p=203#comment-18</guid>
		<description>well put!!!</description>
		<content:encoded><![CDATA[<p>well put!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BoyOnion</title>
		<link>http://www.skratchboard.com/2009/01/top-10-things-to-change-about-the-iphone/comment-page-1/#comment-16</link>
		<dc:creator>BoyOnion</dc:creator>
		<pubDate>Sun, 04 Jan 2009 17:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.skratchboard.com/?p=203#comment-16</guid>
		<description>I totally agree with all of the above. The block to innovation of late by Apple is particularly worrisome.</description>
		<content:encoded><![CDATA[<p>I totally agree with all of the above. The block to innovation of late by Apple is particularly worrisome.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
