Live data from Hacker News

Skeuocard

kenkeiter.com

101–110 of 206 posts

Re: Skeuocard

#101
I love this. couple of things you may want to test - either show all the fields (cc number, exp, name etc) by default, or dont show the name, expiration fields until the credit card number has been filled... its slightly surprising that the other fields show up after entering 5 or 6 digits... also, it is not very clear that I can click and enter the name, expiration date (as it was for cc number)... you may want to move the user directly to the next field after they have entered the previous field.

Re: Skeuocard

#102
After the last number is entered, you should auto focus the NAME field, then EXP DATE or the purchaser won't know what to do. People may think... hey, it guess my card type, how come it's not automatically showing my name?

Re: Skeuocard

#103

Earlier quoted context omitted.

Thank you for being willing to test it! This isn't something I'm making money off of, nor is it something I feel the need to ram down people's throats -- I just wanted to try something people hadn't seen before. If it works, and people like it, great! I'm glad to have helped a little. Please let me know if you run into any trouble (my Twitter and email are on the site).

Hi Ken, it looks great! Unfortunately, for unrecognised card types it makes it impossible to proceed. I have just tried a maestro card number (beginning 6759) and am unable to enter any of the additional details (expiry, etc). It may be worth adding a generic fallback for cards that are not recognised to account for unexpected edge cases. Keep up the good work!

GREAT CATCH! Thank you. I totally missed Maestro Card as a product. I'll get it added ASAP. The fallback is a good idea, too!

Glad you liked it :)

Re: Skeuocard

#105
post #70

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…

> 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…

Hi. My team is responsible for the checkout process at a large company. I won't give exact numbers, but more than $100m goes through our teams two pages.

>by the time I'm entering my credit card details, I'm already "converted".

Our numbers say otherwise. Optimization of our checkout page is a huge deal any change, even text, comes under scrutiny, and for good (i.e. measurable) reason.

Would I put this demo on our page? If the bugs and confusion can be fixed, I might try it for a very small test group and see what happens. Not sure the confusion can be fixed though.

Re: Skeuocard

#106
post #73

Earlier quoted context omitted.

> Agreed, I stumbled for a second before realizing I could type a name in the card I didn't realize this until I read your comment.

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.

Re: Skeuocard

#107
You could two-way bind this with a traditional payment form and end up with something that's useful in the traditional case (feedback about whether the data you're typing is going in the right place), and may delight users who understand what they're seeing and choose to interact with it.

Re: Skeuocard

#109

On my iPad the auto progression doesn't work properly and the keyboard is hidden after each field. You have to tap all over the credit card. I gave up after the fourth extraneous tap. So I guess "why aren't all credit card forms like this" is because people use iPads. (In all seriousness, great idea but disappointing first impression.)

That's really good feedback. I actually hadn't tested on iPad, believe it or not -- I created a ticket on it! https://github.com/kenkeiter/skeuocard/issues/28

Good luck. Apple purposefully disables the ability to control where the keyboard is entering text. AFAIK there's no workaround (I’d love to know if there is!)

Re: Skeuocard

#110
The security code on the backside could use some improving on how it looks. Other than that, this is a really cool idea!
Post reply on HN