<?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: Apple: steal this design</title>
	<atom:link href="http://watchingapple.com/2008/05/apple-steal-this-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://watchingapple.com/2008/05/apple-steal-this-design/</link>
	<description>Thoughts about Apple and design</description>
	<lastBuildDate>Wed, 16 Mar 2011 02:32:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Dennis Lorson</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6563</link>
		<dc:creator>Dennis Lorson</dc:creator>
		<pubDate>Sun, 01 Jun 2008 13:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6563</guid>
		<description>Thanks for your article John; UI design has taken an important place within the development process and the UI has seen many revisions.  We took a lot of cues from Aperture since it is one of the best in its kind, and solves main interaction issues by well thought out metaphors.

Wil, I understand where you&#039;re coming from (the dialog *is* wordy), but actually it has received a lot of thought.  The comparison you make is not correct:
- The semantic difference between &quot;remove&quot; and &quot;delete&quot; is subtle to nonexistent. If Apple wishes to establish a dogmatic difference that is their choice but it is not intuitive at all.  I&#039;m not a native English speaker, but per the OS X Thesaurus: 
9 (Gabriel removed two words) delete, erase, rub out, cross out, ...

Our target users are for a large part International English speakers, so clarity is important here.  That requires avoiding subleties, even if it increases word count.

- The whole use case is different from the Address Book scenario.  In AB, you remove the item and AB asks if it needs to be removed from the library or from the group only.  
The dialog in Macnification offers to remove all items from the library, after having removed the group itself.  An equivalent of this dialog would have no use in AB, as this is never a desired action.
The button label &quot;Remove from Stack&quot; would be meaningless, as the stack itself is being removed anyway.

Again, the differences are subtle but vital, and there might be better solutions to the dialog, but the one Wil suggested is not viable.</description>
		<content:encoded><![CDATA[<p>Thanks for your article John; UI design has taken an important place within the development process and the UI has seen many revisions.  We took a lot of cues from Aperture since it is one of the best in its kind, and solves main interaction issues by well thought out metaphors.</p>
<p>Wil, I understand where you&#8217;re coming from (the dialog *is* wordy), but actually it has received a lot of thought.  The comparison you make is not correct:<br />
- The semantic difference between &#8220;remove&#8221; and &#8220;delete&#8221; is subtle to nonexistent. If Apple wishes to establish a dogmatic difference that is their choice but it is not intuitive at all.  I&#8217;m not a native English speaker, but per the OS X Thesaurus:<br />
9 (Gabriel removed two words) delete, erase, rub out, cross out, &#8230;</p>
<p>Our target users are for a large part International English speakers, so clarity is important here.  That requires avoiding subleties, even if it increases word count.</p>
<p>- The whole use case is different from the Address Book scenario.  In AB, you remove the item and AB asks if it needs to be removed from the library or from the group only.<br />
The dialog in Macnification offers to remove all items from the library, after having removed the group itself.  An equivalent of this dialog would have no use in AB, as this is never a desired action.<br />
The button label &#8220;Remove from Stack&#8221; would be meaningless, as the stack itself is being removed anyway.</p>
<p>Again, the differences are subtle but vital, and there might be better solutions to the dialog, but the one Wil suggested is not viable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak Nulu</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6232</link>
		<dc:creator>Deepak Nulu</dc:creator>
		<pubDate>Thu, 22 May 2008 01:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6232</guid>
		<description>The Macnification and Address Book confirmation dialogs have 3 buttons, and if done &quot;right&quot; (not sure if this is in Apple&#039;s HIG), can be mapped to 3 different keys:

Return: the default button (button with blue background)
Spacebar: the button with blue outline
Escape: the other button.

Escape is usually associated with &quot;Cancel&quot; and hence the &quot;Cancel&quot; button should be the &quot;other&quot; button mentioned above.

Return can be tied to the default button (&quot;Remove from Group&quot;) and Spacebar can be tied to &quot;Delete&quot;.

Also, when apps follow the above &quot;rules&quot;, I have noticed that they are laid out in the following order (left-to-right): button with blue outline, Cancel (button associated with Escape), default button. See the confirmation dialog that appears in TextEdit when you attempt to close an unsaved document.</description>
		<content:encoded><![CDATA[<p>The Macnification and Address Book confirmation dialogs have 3 buttons, and if done &#8220;right&#8221; (not sure if this is in Apple&#8217;s HIG), can be mapped to 3 different keys:</p>
<p>Return: the default button (button with blue background)<br />
Spacebar: the button with blue outline<br />
Escape: the other button.</p>
<p>Escape is usually associated with &#8220;Cancel&#8221; and hence the &#8220;Cancel&#8221; button should be the &#8220;other&#8221; button mentioned above.</p>
<p>Return can be tied to the default button (&#8220;Remove from Group&#8221;) and Spacebar can be tied to &#8220;Delete&#8221;.</p>
<p>Also, when apps follow the above &#8220;rules&#8221;, I have noticed that they are laid out in the following order (left-to-right): button with blue outline, Cancel (button associated with Escape), default button. See the confirmation dialog that appears in TextEdit when you attempt to close an unsaved document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blackburn</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6106</link>
		<dc:creator>John Blackburn</dc:creator>
		<pubDate>Sun, 18 May 2008 17:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6106</guid>
		<description>Though Macnification might offer valuable features that Aperture does not, including, crucially, the ability to read image formats particular to the field, I wasn&#039;t arguing for the value or worth of the Macnification application per se, but instead wanted to comment on how deliberately it borrowed from Apple&#039;s work.</description>
		<content:encoded><![CDATA[<p>Though Macnification might offer valuable features that Aperture does not, including, crucially, the ability to read image formats particular to the field, I wasn&#8217;t arguing for the value or worth of the Macnification application per se, but instead wanted to comment on how deliberately it borrowed from Apple&#8217;s work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Egill</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6105</link>
		<dc:creator>Egill</dc:creator>
		<pubDate>Sun, 18 May 2008 17:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6105</guid>
		<description>I agree with Steven, why would one get an app for $399 that an app on $199 does better?</description>
		<content:encoded><![CDATA[<p>I agree with Steven, why would one get an app for $399 that an app on $199 does better?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6013</link>
		<dc:creator>steven</dc:creator>
		<pubDate>Wed, 14 May 2008 01:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6013</guid>
		<description>I don&#039;t get it... isn&#039;t this just like a really watered down version of Aperture?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t get it&#8230; isn&#8217;t this just like a really watered down version of Aperture?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wil Shipley</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6012</link>
		<dc:creator>Wil Shipley</dc:creator>
		<pubDate>Tue, 13 May 2008 22:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6012</guid>
		<description>Strangely, this app may be aping Apple but they screwed up the words on that dialog -- there are too many!

Address Book does it better: they should just say &quot;Cancel&quot;, &quot;Delete&quot;, and &quot;Remove from Stack&quot;. By drawing a distinction between &quot;DELETE!!!!OMG!&quot; and &quot;remove&quot; Apple can carry the shorthand throughout Address Book and the rest of the system -- I&#039;m removing this app from the dock, but I&#039;m DELETING this file from my hard disk

-Wil</description>
		<content:encoded><![CDATA[<p>Strangely, this app may be aping Apple but they screwed up the words on that dialog &#8212; there are too many!</p>
<p>Address Book does it better: they should just say &#8220;Cancel&#8221;, &#8220;Delete&#8221;, and &#8220;Remove from Stack&#8221;. By drawing a distinction between &#8220;DELETE!!!!OMG!&#8221; and &#8220;remove&#8221; Apple can carry the shorthand throughout Address Book and the rest of the system &#8212; I&#8217;m removing this app from the dock, but I&#8217;m DELETING this file from my hard disk</p>
<p>-Wil</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blackburn</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6005</link>
		<dc:creator>John Blackburn</dc:creator>
		<pubDate>Tue, 13 May 2008 20:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6005</guid>
		<description>Patrick, what&#039;s worked for me in the past has been to clarify the hidden costs of not making design a priority.  If skipping design is perceived as a low- or no-cost alternative--&quot;I skipped design and didn&#039;t suffer at all for it!&quot; or &quot;Our users don&#039;t care about that.&quot;-- it might simply be that the people making the decisions are genuinely unaware of the real costs involved.  Once made aware of those costs, those decision makers can surprise with their new-found appreciation.

For instance, expensive customer support is directly and inversely related to the amount of time spent on design.</description>
		<content:encoded><![CDATA[<p>Patrick, what&#8217;s worked for me in the past has been to clarify the hidden costs of not making design a priority.  If skipping design is perceived as a low- or no-cost alternative&#8211;&#8221;I skipped design and didn&#8217;t suffer at all for it!&#8221; or &#8220;Our users don&#8217;t care about that.&#8221;&#8211; it might simply be that the people making the decisions are genuinely unaware of the real costs involved.  Once made aware of those costs, those decision makers can surprise with their new-found appreciation.</p>
<p>For instance, expensive customer support is directly and inversely related to the amount of time spent on design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://watchingapple.com/2008/05/apple-steal-this-design/comment-page-1/#comment-6002</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 13 May 2008 20:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://watchingapple.com/2008/05/apple-steal-this-design/#comment-6002</guid>
		<description>I agree with the main point - design is important and you should use Apple&#039;s tools so your design is consistent with the user&#039;s expectations.

But what to do if you&#039;re in an organization where (interface) design is not a high priority?</description>
		<content:encoded><![CDATA[<p>I agree with the main point &#8211; design is important and you should use Apple&#8217;s tools so your design is consistent with the user&#8217;s expectations.</p>
<p>But what to do if you&#8217;re in an organization where (interface) design is not a high priority?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

