<?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"
	>
<channel>
	<title>Comments on: 50% slower but still a better experience?</title>
	<atom:link href="http://www.welie.com/thoughts/?feed=rss2&#038;p=9" rel="self" type="application/rss+xml" />
	<link>http://www.welie.com/thoughts/?p=9</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 09 Sep 2010 13:37:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Mike Bradley</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-9760</link>
		<dc:creator>Mike Bradley</dc:creator>
		<pubDate>Sun, 22 Aug 2010 10:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-9760</guid>
		<description>Having owned (for a couple of months!) an iPhone, I too was enamoured with the flick function for setting times and the explicit nature, the responsiveness of the touchscreen and the fun side of the interactions required to operate it. However, as a regular user of the calendar function, I found I couldn't tolerate the length of time to enter a new appointment, which works similar to the alarm, but takes even longer (as a task, not just on an iPhone) as you have to enter more data. I do think Apple have done an outstanding job to move the interaction possibilities through touchscreen away from the 'lets modify what we'd do with a keypad/board' to optimisation for a large majority of users who enjoy and get satisfaction from the somewhat playful implementation. Although the opportunity exists for different implementations of interface for different groups of users  per Alex's comment would seem like a logical next step.</description>
		<content:encoded><![CDATA[<p>Having owned (for a couple of months!) an iPhone, I too was enamoured with the flick function for setting times and the explicit nature, the responsiveness of the touchscreen and the fun side of the interactions required to operate it. However, as a regular user of the calendar function, I found I couldn&#8217;t tolerate the length of time to enter a new appointment, which works similar to the alarm, but takes even longer (as a task, not just on an iPhone) as you have to enter more data. I do think Apple have done an outstanding job to move the interaction possibilities through touchscreen away from the &#8216;lets modify what we&#8217;d do with a keypad/board&#8217; to optimisation for a large majority of users who enjoy and get satisfaction from the somewhat playful implementation. Although the opportunity exists for different implementations of interface for different groups of users  per Alex&#8217;s comment would seem like a logical next step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-2315</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 02 Sep 2009 11:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-2315</guid>
		<description>Providing an alternative (i.e. link 'use traditional add alarm dialogue') for iPhone dialogue would be great.</description>
		<content:encoded><![CDATA[<p>Providing an alternative (i.e. link &#8216;use traditional add alarm dialogue&#8217;) for iPhone dialogue would be great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maritza</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-2252</link>
		<dc:creator>Maritza</dc:creator>
		<pubDate>Mon, 24 Aug 2009 18:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-2252</guid>
		<description>Good article, and nice relatable examples, since so many people own cellphones. One thing I haven't seen mentioned here, is the target group definition. 
I think that serves to explain why the iPhone UI is so successful for iPhone users, since the iPhone by its very nature is designed for a cool, funky and fun market segment. 
The Nokia interface, on the other hand, has for many years evolved into a prime example of Nordic efficiency, aimed primarily at business and casual users of phones who just want to get the job done and don't want to be bothered by too many bits and bobbles.
I own a Nokia E71, considered by many to be one of the most efficient smartphones in the marketplace, with all the functionality of an iPhone, without the glitz and glamour. I'm thrilled with my E71, because I chose it to suit my tastes and purposes.
So neither interface is fundamantelly "wrong" - just aimed at different user groups - and both designs show a careful consideration of the ideal user for the particular device.</description>
		<content:encoded><![CDATA[<p>Good article, and nice relatable examples, since so many people own cellphones. One thing I haven&#8217;t seen mentioned here, is the target group definition.<br />
I think that serves to explain why the iPhone UI is so successful for iPhone users, since the iPhone by its very nature is designed for a cool, funky and fun market segment.<br />
The Nokia interface, on the other hand, has for many years evolved into a prime example of Nordic efficiency, aimed primarily at business and casual users of phones who just want to get the job done and don&#8217;t want to be bothered by too many bits and bobbles.<br />
I own a Nokia E71, considered by many to be one of the most efficient smartphones in the marketplace, with all the functionality of an iPhone, without the glitz and glamour. I&#8217;m thrilled with my E71, because I chose it to suit my tastes and purposes.<br />
So neither interface is fundamantelly &#8220;wrong&#8221; - just aimed at different user groups - and both designs show a careful consideration of the ideal user for the particular device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 蹲乐 UED &#187; Blog Archive &#187; 牺牲操作时间来提升用户体验？</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-1979</link>
		<dc:creator>蹲乐 UED &#187; Blog Archive &#187; 牺牲操作时间来提升用户体验？</dc:creator>
		<pubDate>Fri, 24 Jul 2009 03:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-1979</guid>
		<description>[...] 原文转自：50% slower but still a better experience? [...]</description>
		<content:encoded><![CDATA[<p>[...] 原文转自：50% slower but still a better experience? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JH</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-1597</link>
		<dc:creator>JH</dc:creator>
		<pubDate>Sat, 30 May 2009 12:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-1597</guid>
		<description>good example for fun over effectivness... I think it is relativly new anyway that applications are developed so that it is fun using them instead of just being a good, efficient, working application. And with the whole RIA world, this is even simple to do...

JH</description>
		<content:encoded><![CDATA[<p>good example for fun over effectivness&#8230; I think it is relativly new anyway that applications are developed so that it is fun using them instead of just being a good, efficient, working application. And with the whole RIA world, this is even simple to do&#8230;</p>
<p>JH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iaax Page</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-825</link>
		<dc:creator>Iaax Page</dc:creator>
		<pubDate>Wed, 14 Jan 2009 22:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-825</guid>
		<description>I like this article very much, and I believe you did a great job explaining the balance between IxD principles.

Keep on the good work.

P.S.
Steve Jobs Quotes on Design:
1) A lot of times, people don't know what they want until you show it to them.
2) Design is not how it looks and how it feels. Design is how it works.

Iaax Page
Software, Ingenieria y Diseño</description>
		<content:encoded><![CDATA[<p>I like this article very much, and I believe you did a great job explaining the balance between IxD principles.</p>
<p>Keep on the good work.</p>
<p>P.S.<br />
Steve Jobs Quotes on Design:<br />
1) A lot of times, people don&#8217;t know what they want until you show it to them.<br />
2) Design is not how it looks and how it feels. Design is how it works.</p>
<p>Iaax Page<br />
Software, Ingenieria y Diseño</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilker berkman</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-634</link>
		<dc:creator>ilker berkman</dc:creator>
		<pubDate>Tue, 23 Dec 2008 08:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-634</guid>
		<description>sorry, not soap, it should be soup!</description>
		<content:encoded><![CDATA[<p>sorry, not soap, it should be soup!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilker berkman</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-633</link>
		<dc:creator>ilker berkman</dc:creator>
		<pubDate>Tue, 23 Dec 2008 08:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-633</guid>
		<description>Your conclusions on task frequency and relative time are completely right. But something is missing in this article: Why it is more fun to use iPhone?
In my opnion, the power of direct manipulation makes iPhone alarm set interface more "fun to use". Even it is possible to add iPhone like wheels on Nokia interface, they still need to be controlled by arrow/direction keys on Nokia keyboard. User can not have an experience of directly "touching" the wheels. iPhone touchscreen technology makes it possible. It is more natural (and less effective) to use your fingers instead of a spoon while eating soap.</description>
		<content:encoded><![CDATA[<p>Your conclusions on task frequency and relative time are completely right. But something is missing in this article: Why it is more fun to use iPhone?<br />
In my opnion, the power of direct manipulation makes iPhone alarm set interface more &#8220;fun to use&#8221;. Even it is possible to add iPhone like wheels on Nokia interface, they still need to be controlled by arrow/direction keys on Nokia keyboard. User can not have an experience of directly &#8220;touching&#8221; the wheels. iPhone touchscreen technology makes it possible. It is more natural (and less effective) to use your fingers instead of a spoon while eating soap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Experience Defined</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-537</link>
		<dc:creator>The Experience Defined</dc:creator>
		<pubDate>Sat, 29 Nov 2008 17:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-537</guid>
		<description>[...] Martjin Van Welie writes an excellent little snippet on the differences between setting an alarm on the iPhone interface and the Nokia interface.  The vast majority of User Experience experts I know probably would have assumed that speed and responsiveness was a top priority to test in a lab.  But it&#8217;s very important to note the although it was faster to set up an alarm on the Nokia, the iPhone interface &#8216;feels&#8217; faster and more responsive.  To me, this is the sign of someone who truly understands the human experience.  The Nokia interface is so clumsy and unpolished that it literally &#8216;feels&#8217; less responsive, even though it&#8217;s actually a more utilitarian approach. [...]</description>
		<content:encoded><![CDATA[<p>[...] Martjin Van Welie writes an excellent little snippet on the differences between setting an alarm on the iPhone interface and the Nokia interface.  The vast majority of User Experience experts I know probably would have assumed that speed and responsiveness was a top priority to test in a lab.  But it&#8217;s very important to note the although it was faster to set up an alarm on the Nokia, the iPhone interface &#8216;feels&#8217; faster and more responsive.  To me, this is the sign of someone who truly understands the human experience.  The Nokia interface is so clumsy and unpolished that it literally &#8216;feels&#8217; less responsive, even though it&#8217;s actually a more utilitarian approach. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Blog Archive &#187; Workshop Patterns, M. van Welie</title>
		<link>http://www.welie.com/thoughts/?p=9#comment-371</link>
		<dc:creator>&#187; Blog Archive &#187; Workshop Patterns, M. van Welie</dc:creator>
		<pubDate>Sat, 27 Sep 2008 20:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.welie.com/thoughts/?p=9#comment-371</guid>
		<description>[...] die Martijn gaf de elementen van een goede user experience, vond ik erg verhelderend. Vooral het voorbeeld met het instellen van de wekker op een iPhone en een Nokia heeft mijn kijk op usability veranderd. Normaliter had ik als streven [...]</description>
		<content:encoded><![CDATA[<p>[...] die Martijn gaf de elementen van een goede user experience, vond ik erg verhelderend. Vooral het voorbeeld met het instellen van de wekker op een iPhone en een Nokia heeft mijn kijk op usability veranderd. Normaliter had ik als streven [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
