121–130 of 206 posts
Earlier quoted context omitted.
> That fancy CC form will NOT sell a single thing. It will however stop people from paying. It does nothing to convert. Exactly. This isn't a usability improvement, it's fluff. If you want to see an actual usability improvement, look at what Stripe has done with jQuery.payment: https://github.com/stripe/jquery.payment A good example is in their Checkout javascript component: https://stripe.com/docs/checkout
You might even say, it's skeuomorphism.
I would be concerned about reducing conversions though. Unfamiliarity can be scary.
One annoyance for me - I can't hit Command-A to select everything and start over. I'm also annoyed generally by auto-advancing text fields, though this implementation seems to work around some of the issues.
Earlier quoted context omitted.
This was the primary weak point in the implementation. Expecting users to recognize that they can click on the static-looking fields on the card (or relying on them to use tab to move between fields) does not pass the grandma test. It'd be great if you detected when a field had been fully filled out and moved to the next one automatically.
I think blind people / screen readers might have difficulty with this interface, too. It's important to keep accessibility in mind when designing futuristic interfaces.
Enough with the grey text. #contrastrebellion http://www.contrastrebellion.com/
- ALL of the inputs should look like inputs and only after a user has put in their information should the input ui disappear and the text be shown as it is on a real credit card. Otherwise the ability to enter your name and expiration is ambiguous.
- I don't like how AFTER you enter your full credit card number, the input fields become segregated, trying to change the credit card number becomes difficult as you now have to click on each of the 4 new text fields to enter a new credit card number. (If a card fails to go through a user might try to use a new one). Yes you can just hold down BackSpace and it will travel from field to field deleting the number but that's not obvious for a user to figure out. Don't segregate the numbers into separate fields just leave them in one.
I believe there's an algorithm to determine if a card number is valid (before determining if the other credentials are correct). Implementing that would probably be the most useful thing you could do in Skeuocard, as it helps people find typos in an otherwise inscrutable list of numbers.
Upvoting because this is so beautifully executed and I'd love to see people test this out on their checkout process. That said, my experience indicates that this is not going to convert well. To mirror the author's own quote: "Every question a user has to ask themselves during the checkout process is another reason for them not to complete it." What's presented here is a drastically different experience from the norm…