I have read reports that go in both directions. My personal experience has favored certain implementations of single page checkout.
I think the question cannot be simply "single page" vs. "multi page" checkout. The total experience brings in a lot of variables. I have implemented single-page checkout which consisted of essentially an accordion of "steps" to complete within the checkout. The result was a very responsive "wizard" of sorts, which only revealed subsequent options as a result of previous selections, which also is a way of utilizing progressive disclosure and "wizard"-like behavior. I'm sure the response to this will vary by audience, among other things. If at all possible, I would at least do an a/b split test between a "multi-page" checkout and your "single-page" checkout. A step further would be an experiment pitting several different interaction designs to find the optimal scenario for your audience. IMO, even a multi-page checkout might benefit from loading subsequent pages via ajax, to increase responsiveness, and reduce delay, but there again, a well-planned/executed pause might end up working in your favor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46724 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
