<?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&#8217;s Checkout: Credit Card Flaws</title>
	<atom:link href="http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/</link>
	<description>We are an Information Architecture and UX Design firm in Toronto and we are experts at putting users at the centre of digital development and design, helping you create online experiences that resonate, motivate, and compel.</description>
	<lastBuildDate>Fri, 18 Nov 2011 14:48:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: jabbett</title>
		<link>http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/comment-page-1/#comment-45</link>
		<dc:creator>jabbett</dc:creator>
		<pubDate>Wed, 23 Dec 2009 19:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitymatters.com/?p=247#comment-45</guid>
		<description>I don&#039;t like being asked for information that a computer can easily figure out, but I do like getting confirmation that the system has understood my data as I type it in.

Recognizing credit card type is one good example; figuring out city and state based on ZIP is a better one.

They should make all the logos grayscale to begin with, and then colorize/highlight the proper logo when it&#039;s detected.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like being asked for information that a computer can easily figure out, but I do like getting confirmation that the system has understood my data as I type it in.</p>
<p>Recognizing credit card type is one good example; figuring out city and state based on ZIP is a better one.</p>
<p>They should make all the logos grayscale to begin with, and then colorize/highlight the proper logo when it&#8217;s detected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Dronski</title>
		<link>http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/comment-page-1/#comment-42</link>
		<dc:creator>Bob Dronski</dc:creator>
		<pubDate>Wed, 23 Dec 2009 00:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitymatters.com/?p=247#comment-42</guid>
		<description>I would consider moving the CC icons to below the input fields.  That would give you a visual reminder of what cc&#039;s are accepted without the incentive to click.  You could still do the fade confirmation.

Very interesting take!</description>
		<content:encoded><![CDATA[<p>I would consider moving the CC icons to below the input fields.  That would give you a visual reminder of what cc&#8217;s are accepted without the incentive to click.  You could still do the fade confirmation.</p>
<p>Very interesting take!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoffrey Grosenbach</title>
		<link>http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/comment-page-1/#comment-41</link>
		<dc:creator>Geoffrey Grosenbach</dc:creator>
		<pubDate>Tue, 22 Dec 2009 23:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitymatters.com/?p=247#comment-41</guid>
		<description>I renewed my iPhone developer certificate today and was frustrated by the placement of the submit buttons during the checkout process. 

They work down the page until the very end, when you have to find the &quot;Finalize Checkout&quot; button up at the top right.

It&#039;s as if they are trying to teach you to work top to bottom only to throw a curve at the end by making you find the last button in a completely different place.</description>
		<content:encoded><![CDATA[<p>I renewed my iPhone developer certificate today and was frustrated by the placement of the submit buttons during the checkout process. </p>
<p>They work down the page until the very end, when you have to find the &#8220;Finalize Checkout&#8221; button up at the top right.</p>
<p>It&#8217;s as if they are trying to teach you to work top to bottom only to throw a curve at the end by making you find the last button in a completely different place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eren Emre Kanal</title>
		<link>http://www.usabilitymatters.com/2009/12/22/apples-checkout-form-credit-card-flaws/comment-page-1/#comment-40</link>
		<dc:creator>Eren Emre Kanal</dc:creator>
		<pubDate>Tue, 22 Dec 2009 23:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitymatters.com/?p=247#comment-40</guid>
		<description>I believe that asking for card type was a security issue. If someone&#039;s card number has been stolen (from a web site database) the thief probably will have no idea which type it is. Of course someone who knows about algorithm of CCs would solve it in seconds but most couldn&#039;t.

Now with the security code and other technologies, this may not be necessary anymore.

These are my thoughts about the card type issue, I actually have no official information about it.

About the clickable card images, you are right. That&#039;d be a good feature. On the other hand, I personally don&#039;t look any place to select my card type. I believe that asking for something that we don&#039;t need at all, is unnecessary. Better solution would be having the icons in some other place just to show they accept those.</description>
		<content:encoded><![CDATA[<p>I believe that asking for card type was a security issue. If someone&#8217;s card number has been stolen (from a web site database) the thief probably will have no idea which type it is. Of course someone who knows about algorithm of CCs would solve it in seconds but most couldn&#8217;t.</p>
<p>Now with the security code and other technologies, this may not be necessary anymore.</p>
<p>These are my thoughts about the card type issue, I actually have no official information about it.</p>
<p>About the clickable card images, you are right. That&#8217;d be a good feature. On the other hand, I personally don&#8217;t look any place to select my card type. I believe that asking for something that we don&#8217;t need at all, is unnecessary. Better solution would be having the icons in some other place just to show they accept those.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

