<?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: Why is Apple discouraging interface consistency?</title>
	<atom:link href="http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Thu, 18 Feb 2010 14:38:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Danny</title>
		<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/comment-page-1/#comment-951</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Wed, 07 Oct 2009 02:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=616#comment-951</guid>
		<description>Long live the BlackBerry (Don&#039;t Shoot, only joking)</description>
		<content:encoded><![CDATA[<p>Long live the BlackBerry (Don&#8217;t Shoot, only joking)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Ziarek</title>
		<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/comment-page-1/#comment-906</link>
		<dc:creator>Nathan Ziarek</dc:creator>
		<pubDate>Mon, 21 Sep 2009 16:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=616#comment-906</guid>
		<description>The initial dock apps -- Mail, Safari, iPod and Phone -- have a special place in Apple&#039;s pecking order. As the essential applications, my guess is Apple considers them above replacement. Even with the change to allow non-Safari browsers on the App Store, a quick look didn&#039;t look like any used Mozilla or Opera back ends. They&#039;re just new faces on the same WebKit view.

I&#039;m not sure if there is anything deeper than that. My hope would be that Apple would prefer to integrate Google Voice functionality directly into the Phone and Messages applications. Not likely, but I can dream.</description>
		<content:encoded><![CDATA[<p>The initial dock apps &#8212; Mail, Safari, iPod and Phone &#8212; have a special place in Apple&#8217;s pecking order. As the essential applications, my guess is Apple considers them above replacement. Even with the change to allow non-Safari browsers on the App Store, a quick look didn&#8217;t look like any used Mozilla or Opera back ends. They&#8217;re just new faces on the same WebKit view.</p>
<p>I&#8217;m not sure if there is anything deeper than that. My hope would be that Apple would prefer to integrate Google Voice functionality directly into the Phone and Messages applications. Not likely, but I can dream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Walsh</title>
		<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/comment-page-1/#comment-901</link>
		<dc:creator>Josh Walsh</dc:creator>
		<pubDate>Mon, 21 Sep 2009 14:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=616#comment-901</guid>
		<description>@Jonathan - You&#039;re absolutely right.  The letters to the FCC sound as though Apple&#039;s is afraid of an application which duplicates native functionality of the App.

Developers duplicate native functionality on the mac all the time without Apple whining.   There&#039;s something deeper going on.</description>
		<content:encoded><![CDATA[<p>@Jonathan &#8211; You&#8217;re absolutely right.  The letters to the FCC sound as though Apple&#8217;s is afraid of an application which duplicates native functionality of the App.</p>
<p>Developers duplicate native functionality on the mac all the time without Apple whining.   There&#8217;s something deeper going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbvanhorn</title>
		<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/comment-page-1/#comment-900</link>
		<dc:creator>dbvanhorn</dc:creator>
		<pubDate>Mon, 21 Sep 2009 13:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=616#comment-900</guid>
		<description>J.Penn hits the nail on the head IMO. 

Watch out Apple you&#039;re starting to sound like those whiny guys in Seattle when some one comes along and challenges your &#039;standard&#039;.... with great innovation. 

In technology, what goes around, comes around. Apple needs to be able to dance with all partners. Call your next product Rita Hayworth in fact...

She danced with all the greats...backwards, and in heels. 

Cowboy up Apple.</description>
		<content:encoded><![CDATA[<p>J.Penn hits the nail on the head IMO. </p>
<p>Watch out Apple you&#8217;re starting to sound like those whiny guys in Seattle when some one comes along and challenges your &#8217;standard&#8217;&#8230;. with great innovation. </p>
<p>In technology, what goes around, comes around. Apple needs to be able to dance with all partners. Call your next product Rita Hayworth in fact&#8230;</p>
<p>She danced with all the greats&#8230;backwards, and in heels. </p>
<p>Cowboy up Apple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Penn</title>
		<link>http://www.designinginteractive.com/user-experience/why-is-apple-discouraging-interface-consistency/comment-page-1/#comment-899</link>
		<dc:creator>Jonathan Penn</dc:creator>
		<pubDate>Mon, 21 Sep 2009 12:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=616#comment-899</guid>
		<description>Yeah, the chat bubble controversy is strange.  Why wouldn&#039;t they treat the chat bubble as a device wide &quot;control&quot; that displays conversation threads?

But, from my reading of the letters to the FCC from both parties, Apple isn&#039;t discouraging consistency with Google Voice as much as it doesn&#039;t want Google to do a phone-like app at all on the iPhone.  There wasn&#039;t any wording in their letter that consistency was at issue.  They were concerned with confusion from the overlap of functionality between the two pieces of software.  Google&#039;s phone doesn&#039;t just use interface elements from Apple&#039;s phone app, it could be a *replacement* for Apple&#039;s phone app.</description>
		<content:encoded><![CDATA[<p>Yeah, the chat bubble controversy is strange.  Why wouldn&#8217;t they treat the chat bubble as a device wide &#8220;control&#8221; that displays conversation threads?</p>
<p>But, from my reading of the letters to the FCC from both parties, Apple isn&#8217;t discouraging consistency with Google Voice as much as it doesn&#8217;t want Google to do a phone-like app at all on the iPhone.  There wasn&#8217;t any wording in their letter that consistency was at issue.  They were concerned with confusion from the overlap of functionality between the two pieces of software.  Google&#8217;s phone doesn&#8217;t just use interface elements from Apple&#8217;s phone app, it could be a *replacement* for Apple&#8217;s phone app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
