Live data from Hacker News

Skeuocard

kenkeiter.com

111–120 of 206 posts

Re: Skeuocard

#111

Earlier quoted context omitted.

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 :)

Don't forget UnionPay either then :)

Re: Skeuocard

#113
I never thought of this before, but the first 4 digits of my credit card number revealing the issuing bank seems insecure to me. That's not a fault of the op's program, of course.

Re: Skeuocard

#114

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.)

Second this. My bank does also splits the entry fields for the digits when there is a specific format, and it's a real PITA.

For those not on a ipad now, what happens is when trying to tap 5 digits in a row for 4 digit field: the keyboard disappears at the fourth tap, and the fith tap misses it's target and lands on the page.

If the 'somewhere' happens to be a link (i.e. the 'view on github' link on the left if right below the '4' when the keyboard is displayed) you get out of the page, and have to start over again. Trying to enter important information is stressful enough, getting out of the page every pack of digits and start over all again is a punishment in itself.

Re: Skeuocard

#115
post #95

[Edit: original thread title was "why isn't every CC form like this?"] Because it's completely unneeded. Typical web designer wet dream. Fancy-schmancy visual design fluff, robbing screen real-estate and bandwidth for a freaking "credit card" background image, and will it still work even 2 or 5 years from now when all web dev standards have once again turned 180° and future browsers render stuff like this way-off or…

Agreed. As a designer, I don't want to waste space with this for two form inputs, not including the CVV. On pages asking for your CC information, there's generally a lot more than just this going on, and the possibility it creates confusion for those who think it is merely a graphic representing a card, and not part of the process itself, during the most important aspect of the sale just doesn't fly with me.

Re: Skeuocard

#116
post #51

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

Re: Skeuocard

#117
Interesting idea.

One bug I noticed: if you enter one of the sample numbers such that the number splits into multiple fields, then backspace starting from the end, you'll end up moved to the beginning of the first field with the first few digits still filled in, rather than backspacing over them.

More generally, any time you construct your own custom input rather than using browser input fields as designed, you end up with this kind of brokenness because you have to reimplement browser logic.

I'd love to see an , with an input-creditcard.js polyfill, and native support added to browsers. On platforms that already know your credit card number, this would allow for simple auto-fill of all relevant information. This would also make life easier for things like Google Wallet that construct virtual credit cards for you, and it would allow for browser extensions that integrate with credit-card vendors to produce one-time tokens.

Re: Skeuocard

#118
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'd be grateful if you would be kind enough to share results after testing. Happy to sign-up to a mailing list to be notified.

Re: Skeuocard

#119
I have a bit of a pet peeve for apps that try to customize form fields, because they almost always get the corner cases wrong. Here, for instance, select all doesn't work as expected. (In fact, selection doesn't work at all. Skeuocard, like many overly-clever widgets, will overwrite your selection to put the cursor where it thinks it should go.
Post reply on HN