New answers tagged checkout
Sorry to use the Answer function, but I can't add comments yet. It's not clear from your question what platforms you're designing for, but assuming that you're designing for at least both iOS and Android I think you will have useability issues with the first option. For example, swiping from the top right on an iOS device is likely to trigger the ...
An alternative is to have pricing levels e.g. single user, 2-10 users, 11-100 users with price breaks. This would give your users better understanding of what they are spending, would make accounting easier, etc. etc.
There is no reason to add a field into a form if you dont really need that information. In e-commerce the average abandonment rate is near at 70% (contact form could have some analogies). In each guidelines for form designing, one of the main suggestions is ever to make the form as simply as possible, avoiding all unnecessary requests.
In 2010, the Post Office stopped the requirement for including County in a postal address so it is indeed not necessary to keep it for the purposes of 'a complete address'. Currently on the Post Office help system, the answer to the question Should I use a county name in my address? is: When you address your mail, you don’t need to include a county name ...
In my experience, checkout process UI design is very complicated once you get to the details. And login/ signup is tricky from legal and technical perspective. Based on personal experience with checkout design (I have no knowledge of Amazon's reasoning behind their design), considerations that may have played a role: Many aspects of the checkout process ...
Top 50 recent answers are included