<?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: When Web Developers Dont Consider Usability</title> <atom:link href="http://www.getelastic.com/developer-usability/feed/" rel="self" type="application/rss+xml" /><link>http://www.getelastic.com/developer-usability/</link> <description>#1 Subscribed Ecommerce Blog</description> <lastBuildDate>Thu, 09 Feb 2012 02:57:16 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.2.1</generator> <item><title>By: Norton</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-64290</link> <dc:creator>Norton</dc:creator> <pubDate>Fri, 04 Nov 2011 14:08:50 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-64290</guid> <description>Yes, privacy can be an issue with cookie based carts.  If someone shops on a shared computer (computer lab, coffee shop, etc.) and then someone else visits the same site on that computer, the cart would persist to the 2nd user.  So, you wouldn&#039;t want to store personal information, payment information, etc.
Input fields have the same problem and we&#039;ve needed to explicitly code our payment textboxes so that they don&#039;t prompt the user with the previously entered information.
We&#039;ve used a cart stored in the session state for years and have lamented the fact that users lose the cart.  (Our shared server re-boots the application once every 24 hours or so, which wipes out all session data.)  This is a big problem these days, particularly at the holidays, when customers use their cart as a sort of wish list, while deciding what to get and where to get it.  So, we&#039;re implementing a cookie based cast and will use the session state cart only for those who do not accept cookies.  (Our system will check if they accept cookies and store the cart information accordingly.)
We&#039;ll also need to code something to make it clear that a previously saved cart exists, to prevent people from accidentally buying something that they didn&#039;t know was in their cart from a previous session.
Writing a custom cart is certainly not a simple thing.</description> <content:encoded><![CDATA[<p>Yes, privacy can be an issue with cookie based carts.  If someone shops on a shared computer (computer lab, coffee shop, etc.) and then someone else visits the same site on that computer, the cart would persist to the 2nd user.  So, you wouldn&#8217;t want to store personal information, payment information, etc.</p><p>Input fields have the same problem and we&#8217;ve needed to explicitly code our payment textboxes so that they don&#8217;t prompt the user with the previously entered information.</p><p>We&#8217;ve used a cart stored in the session state for years and have lamented the fact that users lose the cart.  (Our shared server re-boots the application once every 24 hours or so, which wipes out all session data.)  This is a big problem these days, particularly at the holidays, when customers use their cart as a sort of wish list, while deciding what to get and where to get it.  So, we&#8217;re implementing a cookie based cast and will use the session state cart only for those who do not accept cookies.  (Our system will check if they accept cookies and store the cart information accordingly.)</p><p>We&#8217;ll also need to code something to make it clear that a previously saved cart exists, to prevent people from accidentally buying something that they didn&#8217;t know was in their cart from a previous session.</p><p>Writing a custom cart is certainly not a simple thing.</p> ]]></content:encoded> </item> <item><title>By: free vpn</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19135</link> <dc:creator>free vpn</dc:creator> <pubDate>Thu, 05 Nov 2009 15:01:55 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19135</guid> <description>He probably has &quot;X&quot; amount of dollars to spend in this exercise. Make sure he buys at least ten stocks.</description> <content:encoded><![CDATA[<p>He probably has &#8220;X&#8221; amount of dollars to spend in this exercise. Make sure he buys at least ten stocks.</p> ]]></content:encoded> </item> <item><title>By: soccer</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19133</link> <dc:creator>soccer</dc:creator> <pubDate>Fri, 30 Oct 2009 11:40:39 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19133</guid> <description>How will we have money to support millions of more people in the future?</description> <content:encoded><![CDATA[<p>How will we have money to support millions of more people in the future?</p> ]]></content:encoded> </item> <item><title>By: Tim</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19131</link> <dc:creator>Tim</dc:creator> <pubDate>Fri, 14 Aug 2009 19:12:19 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19131</guid> <description>I will bless the day I can work with people like you. Great(!) article and insight. And consider me a returning customer ;)</description> <content:encoded><![CDATA[<p>I will bless the day I can work with people like you. Great(!) article and insight. And consider me a returning customer <img
src='http://www.getelastic.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Linda Bustos</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19129</link> <dc:creator>Linda Bustos</dc:creator> <pubDate>Wed, 12 Aug 2009 17:18:59 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19129</guid> <description>@Michael,
The cookie problem is more of anti-spyware programs that delete cookies on behalf of the user on a regular basis.
Re: persistent carts without cookies, are you referring to session IDs? Yes they carry some security risks if the session URL is somehow bookmarked or shared. This article may be of interest to you in that regard
http://searchsoftwarequality.techtarget.com/news/article/0,289142,sid92_gci1156684,00.html</description> <content:encoded><![CDATA[<p>@Michael,</p><p>The cookie problem is more of anti-spyware programs that delete cookies on behalf of the user on a regular basis.</p><p>Re: persistent carts without cookies, are you referring to session IDs? Yes they carry some security risks if the session URL is somehow bookmarked or shared. This article may be of interest to you in that regard<br
/> <a
href="http://searchsoftwarequality.techtarget.com/news/article/0,289142,sid92_gci1156684,00.html" rel="nofollow">http://searchsoftwarequality.techtarget.com/news/article/0,289142,sid92_gci1156684,00.html</a></p> ]]></content:encoded> </item> <item><title>By: Michael Kimsal</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19127</link> <dc:creator>Michael Kimsal</dc:creator> <pubDate>Wed, 12 Aug 2009 15:01:14 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19127</guid> <description>Couple of questions after reading this:
How many people explicitly and knowingly turn off total cookie support in their browser?
If you try to implement some sort of &#039;persistent cart&#039; experience (somehow without using cookies) what about privacy of people using public systems?  There are privacy concerns that need to be balanced with &#039;usability&#039; which don&#039;t seem to be addressed here.</description> <content:encoded><![CDATA[<p>Couple of questions after reading this:</p><p>How many people explicitly and knowingly turn off total cookie support in their browser?</p><p>If you try to implement some sort of &#8216;persistent cart&#8217; experience (somehow without using cookies) what about privacy of people using public systems?  There are privacy concerns that need to be balanced with &#8216;usability&#8217; which don&#8217;t seem to be addressed here.</p> ]]></content:encoded> </item> <item><title>By: Toucouleur</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19125</link> <dc:creator>Toucouleur</dc:creator> <pubDate>Mon, 10 Aug 2009 10:56:42 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19125</guid> <description>@Inigo = you seems to be a Magento resselers without the knowledge of his own products. Of course you can manage persistent shopping cart, but users won&#039;t have their cart stored for all the time.
As Toby mentioned above, the problem with persistent cart is how we can manage sessions data stored for a long time.
We are currently working on Magento &amp; OsCommerce&#039;s solutions to find out how persistents carts could be improved to manage unregistered shopping carts.</description> <content:encoded><![CDATA[<p>@Inigo = you seems to be a Magento resselers without the knowledge of his own products. Of course you can manage persistent shopping cart, but users won&#8217;t have their cart stored for all the time.</p><p>As Toby mentioned above, the problem with persistent cart is how we can manage sessions data stored for a long time.</p><p>We are currently working on Magento &amp; OsCommerce&#8217;s solutions to find out how persistents carts could be improved to manage unregistered shopping carts.</p> ]]></content:encoded> </item> <item><title>By: Inigo</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19123</link> <dc:creator>Inigo</dc:creator> <pubDate>Mon, 10 Aug 2009 09:53:50 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19123</guid> <description>Or you can go with a package that already allows for persistent shopping carts e.g. Magento.  Add the item to the basket, quit browser, come back and it&#039;s still there in the cart...</description> <content:encoded><![CDATA[<p>Or you can go with a package that already allows for persistent shopping carts e.g. Magento.  Add the item to the basket, quit browser, come back and it&#8217;s still there in the cart&#8230;</p> ]]></content:encoded> </item> <item><title>By: Linda Cramer</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19121</link> <dc:creator>Linda Cramer</dc:creator> <pubDate>Thu, 06 Aug 2009 17:20:31 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19121</guid> <description>I&#039;m not sure customers hate registering. If you know you&#039;ll be back to a site often and you are happy with your experience there. I think registering to save your data is valuable and done by many people who want to save time.</description> <content:encoded><![CDATA[<p>I&#8217;m not sure customers hate registering. If you know you&#8217;ll be back to a site often and you are happy with your experience there. I think registering to save your data is valuable and done by many people who want to save time.</p> ]]></content:encoded> </item> <item><title>By: Anna</title><link>http://www.getelastic.com/developer-usability/comment-page-1/#comment-19119</link> <dc:creator>Anna</dc:creator> <pubDate>Tue, 04 Aug 2009 16:26:02 +0000</pubDate> <guid
isPermaLink="false">http://www.getelastic.com/?p=3875#comment-19119</guid> <description>Its difficult for developers who are new to e commerce to consider usability fully and unfortunately the only way to learn is to make mistakes on peoples sites. Sad but true</description> <content:encoded><![CDATA[<p>Its difficult for developers who are new to e commerce to consider usability fully and unfortunately the only way to learn is to make mistakes on peoples sites. Sad but true</p> ]]></content:encoded> </item> </channel> </rss>
