Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Skeuocard

kenkeiter.com

Post reply on HN
Print view View original

191–200 of 206 posts

Re: Skeuocard

#191

Post by hnal943 »

jarek wrote: post #140
xymostech wrote: post #124

Earlier quoted context omitted.

If you press tab, it at least cycles through all of the input boxes on the front side in an appropriate manner, and you could probably design it to flip over on the next tab press. I'm fairly certain that would make it work with screen readers (but not positive).

It doesn't tab between the input boxes or even show the boxes until it's detected the card type based on first four digits. On initial load you get an input box with "XXXX XXXX XXXX XXXX" and nothing else. It does not look like an average credit card form and a lot of people will be confused "where do I put in my name" when they first see it.

I don't know. The current convention is always to enter the credit card number first, then the name later (usually as part of the billing address). Once you start entering your card, the rest of the information is explained nicely.

Re: Skeuocard

#192

Post by dubcanada »

jasonlotito wrote: post #182
coldtea wrote: post #70

Earlier quoted context omitted.

> That fancy CC form will NOT sell a single thing. It will however stop people from paying. Citation needed. > It does nothing to convert. Beside the point. Any other credit card form I've seen does nothing to convert either -- and it's not it's job: by the time I'm entering my credit card details, I'm already "converted". Most of the objections are dead simple to fix (tab order, 1password), and address nothing inher…

> Citation needed. Unfortunately, I've never published anything to any official standard. I can only go by my experience. That experience involves transactions north of $100M. > Any other credit card form I've seen does nothing to convert either -- and it's not it's job Perhaps I worded it poorly. However, a CC form's job is to convert a potential customer into a paying customer. Just because you've entered your CC d…

Being a little less "blunt" may help a bit. I generally don't start my criticism off with "So..." followed by a list of everything that is wrong with it and then a "THIS WON'T CONVERT" in caps.

I think more likely the reason is people with "north of $100M" in transactions are scared to try something new on their form. When there form clearly works fine as it is. But that doesn't mean exploring new methods is a bad idea. I know a lot of people who are still unsure of what a CVV is. And having a replication of their credit card so they know exactly what goes where would work very well.

Anyways just my 2c's

Re: Skeuocard

#193

Post by fragmede »

aresant wrote: post #8

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…

I'm going to guess that this will actually convert better because it helps answer the most important question a user asks:

Did I enter my freaking CC number right?

For those hunt and peck typists, the larger size, the proper handling of spaces, and the ease of comparing to the actual card makes that so much easier, even for the average users.

I will note that the expiry and name input could be highlighter better - I missed the expiry until I accidentally clicked on it.

For those power shoppers who've memorized their card number, this will still work for them too.

Re: Skeuocard

#194

Post by jasonlotito »

dubcanada wrote: post #192
jasonlotito wrote: post #182

Earlier quoted context omitted.

> Citation needed. Unfortunately, I've never published anything to any official standard. I can only go by my experience. That experience involves transactions north of $100M. > Any other credit card form I've seen does nothing to convert either -- and it's not it's job Perhaps I worded it poorly. However, a CC form's job is to convert a potential customer into a paying customer. Just because you've entered your CC d…

Being a little less "blunt" may help a bit. I generally don't start my criticism off with "So..." followed by a list of everything that is wrong with it and then a "THIS WON'T CONVERT" in caps. I think more likely the reason is people with "north of $100M" in transactions are scared to try something new on their form. When there form clearly works fine as it is. But that doesn't mean exploring new methods is a bad id…

I was trying to be clear. Judging by the OP's response, I think I was successful. But agreed, I could have avoided the So… part. There was really didn't mean anything by that part. Mea culpa.

> I think more likely the reason is people with "north of $100M" in transactions are scared to try something new on their form. When there form clearly works fine as it is.

That's actually far from the truth, at least in my experience. You are constantly looking at how to improve the experience at every level. Between the amount of time a person spends entering in each field, to the errors they get back, and even where the person lives. Everything is scrutinized. Not everything matters, but you keep looking.

> I know a lot of people who are still unsure of what a CVV is.

Yep. And there are ways you can go about resolving that. Hiding the field from the start is a bad idea. There is nothing to suggest that you couldn't also display the back of the credit card below the front.

The most important thing you can do when designing something like this is get real feedback and data. Just because it looks nice doesn't mean it will help.

Re: Skeuocard

#195

Post by pbreit »

jasonlotito wrote: post #44

So… * Didn't realize I had the name and expiration field to enter as well. I thought it was just show casing the number entry. It wasn't until I came back here to HN to read comments that I realized that there was more to the demo. * Tab order was wrong. * 1Password couldn't fill in the data. * No indicator telling me what credit cards you accept. * CVV was hidden. There were several cases where I'd finished filling…

I wanted to like it but I'm not sure it's really better and could be much worse merely from being so different from every other method.

That said, there are some problems: * Amex CVV doesn't allow the proper 4 digits * Tab-order is weird * Confusing because sometimes you tab to next field, sometimes you don't * Name usually not needed since already entered elsewhere (inexplicable why so many checkout forms do this) * Difficult to change card number

Re: Skeuocard

#196

Post by YcombRegBroken »

robflynn wrote: post #154

I'll be sending you a pull request in a day or two. I work with dead, blind, hard of hearing, and visually impaired folks. I see a few places where accessibility could be improved with respect to screen readers. Would you be open to a patch like that?

I swear I'm not a grammar nazi, but I did just spend the past 10 minutes thinking about ideal user interfaces for zombies and vampires. Thanks for that...

Re: Skeuocard

#197

Post by dragonwriter »

YcombRegBroken wrote: post #196
robflynn wrote: post #154

I'll be sending you a pull request in a day or two. I work with dead, blind, hard of hearing, and visually impaired folks. I see a few places where accessibility could be improved with respect to screen readers. Would you be open to a patch like that?

I swear I'm not a grammar nazi, but I did just spend the past 10 minutes thinking about ideal user interfaces for zombies and vampires. Thanks for that...

Not to be a word choice nazi, but I think you mean either "word choice nazi" or "spelling nazi" rather than "grammar nazi", as the post you responded to was grammatically correct but apparently used "dead" in place of "deaf".

Re: Skeuocard

#198

Post by tb303 »

ChrisLTD wrote: post #9
dictum wrote: post #5

>Every question a user has to ask themselves during the checkout process is another reason for them not to complete it. ( http://kenkeiter.com/2013/07/21/redesigning-credit-card-inpu... ) "Wait, where do I put the CVC, name and expiration date?"

To that point, I would consider putting borders on all the entry fields to make it clear where user data goes. It wouldn't be as pretty, but it might be more usable.

Yes, and then I'd consider arranging them on a grid, with predictable tab order, and then I'd consider remove distracting visual ornamentation, and then...

...we have a usable, familiar, industry-tested form of data entry. =D

Post reply on HN