I am glad that you are asking about quickview on ixda. Some months back I was working on a similar project and couldnt find any study related to quickview. When ecommerce sites are increasingly using the quickviews there should be some study done on QV as much as product details pages.
This is anecdotal, but I ran a test on a prototype of it a few years ago for a furniture site we were building. Our implementation of it was confusing and the feedback we were getting wasn't getting us closer to a good result, so we left it off.
Of course, that doesn't mean every implementation of it will have the same results. Shopping for expensive furniture requires a different mindset than shopping for moderately priced clothing (such as at Gap.com).
If you're considering using it for your situation, build a prototype and test it in front of users. Use only as much data and build as much of it out as necessary to conduct the test.
Good point. We just published the Retailer Social Commerce Scorecard (free at http://www.usography.com/scorecard) which links to 100 top retailer product detail screen captures. It's a quick UX overview of 100 design approaches to presenting products, but it doesn't have screen captures of QuickView state. Might be a good idea to add that into the next version.
I am not aware of any research studies, but I would suggest checking out Elastic Path's blog, as they may have touched on quick views in one of their posts. Anecdotally, I've found that quick view's are most helpful when the product decision is image-based (clothing) and less helpful when it's feature-based (like a computer), with shades of gray in between.
Paul Nuschke
Get the feed
Comments
I am glad that you are asking about quickview on ixda. Some months back I was working on a similar project and couldnt find any study related to quickview. When ecommerce sites are increasingly using the quickviews there should be some study done on QV as much as product details pages.
If you find one let me know....
This is anecdotal, but I ran a test on a prototype of it a few years ago for a furniture site we were building. Our implementation of it was confusing and the feedback we were getting wasn't getting us closer to a good result, so we left it off.
Of course, that doesn't mean every implementation of it will have the same results. Shopping for expensive furniture requires a different mindset than shopping for moderately priced clothing (such as at Gap.com).
If you're considering using it for your situation, build a prototype and test it in front of users. Use only as much data and build as much of it out as necessary to conduct the test.
Good point. We just published the Retailer Social Commerce Scorecard (free at http://www.usography.com/scorecard) which links to 100 top retailer product detail screen captures. It's a quick UX overview of 100 design approaches to presenting products, but it doesn't have screen captures of QuickView state. Might be a good idea to add that into the next version.
/pb
I am not aware of any research studies, but I would suggest checking out Elastic Path's blog, as they may have touched on quick views in one of their posts.
Anecdotally, I've found that quick view's are most helpful when the product decision is image-based (clothing) and less helpful when it's feature-based (like a computer), with shades of gray in between.
Paul Nuschke
On Wed, Apr 13, 2011 at 12:04 AM, gthomas10 <gthomas10@gmail.com> wrote: