<?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: Taptu iPhone App: Flick Interface</title>
	<atom:link href="http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/</link>
	<description>Taptu makes it faster to find and share mobile-friendly stuff. It&#039;s the free alternative search machine, tailor made for mobile phones.</description>
	<lastBuildDate>Thu, 18 Mar 2010 09:01:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric Fei</title>
		<link>http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/comment-page-1/#comment-52801</link>
		<dc:creator>Eric Fei</dc:creator>
		<pubDate>Fri, 16 Oct 2009 02:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.taptu.com/?p=1463#comment-52801</guid>
		<description>Hi Marc, Andrew is right, there really shouldn&#039;t be any difficulty in detecting tab vs swipe.  It&#039;s a standard thing in iPhone and being used all over the place.

Another thing is that I don&#039;t find showing card more superior than showing list.  With cards, I don&#039;t know what is next, with list I get to see more at a glance.  Visually it may look better, but functionally, it&#039;s less superior.</description>
		<content:encoded><![CDATA[<p>Hi Marc, Andrew is right, there really shouldn&#8217;t be any difficulty in detecting tab vs swipe.  It&#8217;s a standard thing in iPhone and being used all over the place.</p>
<p>Another thing is that I don&#8217;t find showing card more superior than showing list.  With cards, I don&#8217;t know what is next, with list I get to see more at a glance.  Visually it may look better, but functionally, it&#8217;s less superior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew P</title>
		<link>http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/comment-page-1/#comment-51095</link>
		<dc:creator>Andrew P</dc:creator>
		<pubDate>Wed, 09 Sep 2009 10:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.taptu.com/?p=1463#comment-51095</guid>
		<description>Hi Marc,

Almost ALL of Apples applications on the iPhone are built on the standard combined tap / swipe paradigm.  If the taptu app isnt reliably differentiating between a flick and tap event, then there is something wrong.

One example in point is the multi function launch / drag / move / edit of the iPhone home screen.  This screen reliably detects the following actions.

1. Launching an application - the application is only launched when you lift your finger from the screen.

2. Swiping to a different page - if you select an application but swipe, the whole page swipes to the next page.

3. Deleting or Moving an application - if you select an application but dont release or dont swipe, the home screen goes into edit mode.

Being the iphone home screen, it sets the bar of expectation for ALL iPhone / iPod touch apps, and I liken the usability of this screen to the taptu iphone application.

My point is that you comfortably comply to this usability on both the taptu home screen where you swipe or touch the suggested categories and on the image search where you swipe or select an image to view.  However, you picked a different paradigm on the results page where you have a pink button to view the page.

This is why I was tapping the thumbnail and getting frustrated as it didnt load the page as expected.

Andrew</description>
		<content:encoded><![CDATA[<p>Hi Marc,</p>
<p>Almost ALL of Apples applications on the iPhone are built on the standard combined tap / swipe paradigm.  If the taptu app isnt reliably differentiating between a flick and tap event, then there is something wrong.</p>
<p>One example in point is the multi function launch / drag / move / edit of the iPhone home screen.  This screen reliably detects the following actions.</p>
<p>1. Launching an application &#8211; the application is only launched when you lift your finger from the screen.</p>
<p>2. Swiping to a different page &#8211; if you select an application but swipe, the whole page swipes to the next page.</p>
<p>3. Deleting or Moving an application &#8211; if you select an application but dont release or dont swipe, the home screen goes into edit mode.</p>
<p>Being the iphone home screen, it sets the bar of expectation for ALL iPhone / iPod touch apps, and I liken the usability of this screen to the taptu iphone application.</p>
<p>My point is that you comfortably comply to this usability on both the taptu home screen where you swipe or touch the suggested categories and on the image search where you swipe or select an image to view.  However, you picked a different paradigm on the results page where you have a pink button to view the page.</p>
<p>This is why I was tapping the thumbnail and getting frustrated as it didnt load the page as expected.</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Holgate</title>
		<link>http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/comment-page-1/#comment-51069</link>
		<dc:creator>Marc Holgate</dc:creator>
		<pubDate>Tue, 08 Sep 2009 15:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.taptu.com/?p=1463#comment-51069</guid>
		<description>Hi Andrew,
Thanks for the suggestion.

Unfortunately, due to sensitivity of the iPhone&#039;s &#039;touch&#039; event, it&#039;s not possible for the software to reliably differentiate between a horizontal &#039;flick&#039; event and a &#039;tap&#039; event.  We&#039;ve observed many users attempt to flick cards, but those flicks were mistakenly interpreted as taps by the iPhone itself. This resulted in the user being taken to the source site rather than to the next card - very frustrating.

So, to reduce error-rate, we decided to size-down the action hotspot to a pink &#039;go to source&#039; button. 

Hope that helps.</description>
		<content:encoded><![CDATA[<p>Hi Andrew,<br />
Thanks for the suggestion.</p>
<p>Unfortunately, due to sensitivity of the iPhone&#8217;s &#8216;touch&#8217; event, it&#8217;s not possible for the software to reliably differentiate between a horizontal &#8216;flick&#8217; event and a &#8216;tap&#8217; event.  We&#8217;ve observed many users attempt to flick cards, but those flicks were mistakenly interpreted as taps by the iPhone itself. This resulted in the user being taken to the source site rather than to the next card &#8211; very frustrating.</p>
<p>So, to reduce error-rate, we decided to size-down the action hotspot to a pink &#8216;go to source&#8217; button. </p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew P</title>
		<link>http://blog.taptu.com/2009/08/05/taptu-iphone-app-flick-interface/comment-page-1/#comment-51067</link>
		<dc:creator>Andrew P</dc:creator>
		<pubDate>Tue, 08 Sep 2009 14:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.taptu.com/?p=1463#comment-51067</guid>
		<description>Hi Marc,

One thing I find my self constantly doing is just tapping the image thumbnail (above the pink arrow) to navigate to the actual site - It&#039;s a much larger and more intuitive tap zone.

Why not do away with the pink button altogether?

This would then make it consistent with the way you can use the taptu app to navigate images.

Andrew</description>
		<content:encoded><![CDATA[<p>Hi Marc,</p>
<p>One thing I find my self constantly doing is just tapping the image thumbnail (above the pink arrow) to navigate to the actual site &#8211; It&#8217;s a much larger and more intuitive tap zone.</p>
<p>Why not do away with the pink button altogether?</p>
<p>This would then make it consistent with the way you can use the taptu app to navigate images.</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
</channel>
</rss>
