Skeuocard
101–110 of 206 posts
Re: Skeuocard
#102Re: Skeuocard
#103Earlier 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!
Glad you liked it :)
Re: Skeuocard
#104Re: Skeuocard
#105So… * 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…
>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
#106Earlier 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.
Re: Skeuocard
#107Re: Skeuocard
#108Re: Skeuocard
#109On 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