Tag Info

New answers tagged

2

Assuming you want to do right to your customer (and store) by making the payment and shipping flow as short and hassle-less as possible, I'd offer them the option to choice as soon as possible A. 'Quick pay purchase' with PayPal (Or 'x-click purchase', or..) B. Manual check-out (or whomever you like to call the 'native' option) If they choose A, you can ...


7

This is an interesting question. Thanks for asking. I had the exact same idea last year, and after some research and even an A/B test, I chose to stick with the field-set approach. This is based on my own experience with an online shop that actually ships fashion items. So this is about shipping address; not the billing address. Users who place online ...


4

From a UX standpoint, the most important question is whether the user's presaved "auto-fill" will fill in your form. You really need to check whether your single text area will work with such features. If it won't, you've potentially lost a user/customer/petition-signer/whatever. Especially with the prevalence of phone/tablet based users, entering an address ...


16

TL;DR: Use a single text field, store as a single string, show an address label preview. Separate fields have served limited purpose, such as safely identifying the country, town or zip code area someone lives in. They also allowed to enforce some constraints, such as providing a fixed list of countries. They also - in theory - allowed to "reduce the ...


3

I'd imagine address separation boils down to the following: Backend storage, useful for a variety of reasons like reporting Validation of individual elements of the address to ensure correctness (without, imagine the parsing you would have to do) Label printing The last thing you want is someone's credit card information on file, processed, with no way ...



Top 50 recent answers are included