247 votes

Splitting credit card number fields into four different inputs

I would generally always opt for the simplest solution. In this case, one single field for the user to type into. With split fields, such as the 4-box one you propose it adds in an extra cognitive ...
JonW's user avatar
  • 37.4k
145 votes

Splitting credit card number fields into four different inputs

This answer and this answer cover some of the points nicely but for some reason nobody is discussing auto-fill support. Don't use 4 separate fields. First, it's annoying, a lot of those reasons are ...
Jason C's user avatar
  • 2,684
84 votes
Accepted

DD/MM/YY or DD/MM/YYYY?

There is no universally good answer to this question, but there are definitely two pros of YYYY: by showing the two leading numbers you can easily tell e.g. 1911 from 2011, you know exactly where the ...
Dominik Oslizlo's user avatar
66 votes

Splitting credit card number fields into four different inputs

As someone who happens to use virtual credit cards, I'm strongly in favour of a single field. Every time I want to pay, there is a new card number generated for me by the banking app, and it's very ...
Dmitry Grigoryev's user avatar
64 votes

DD/MM/YY or DD/MM/YYYY?

As a rule, it's never OK to use a 2-digit year. If you can prove that using a 4-digit year will cause thousands of babies and cute fluffy bunnies to die horribly, that could be an exception to the ...
Medievalist's user avatar
63 votes
Accepted

What is the most readable way to display a U.S. phone number?

I agree with you that the first is best. Good UX is largely about reducing the cognitive load of a user. (###) ###-#### is a format that, in North America, is unique to phone numbers, so I know as ...
maxathousand's user avatar
  • 19.5k
53 votes

Users entering the wrong decimal separators for US$ amounts

Another option would be for the text field to ignore all non-numeric characters, and display appropriate formatting automatically. For example: User enters '3' -> Text field displays '0.03' User ...
Ghillie Dhu's user avatar
35 votes
Accepted

Users entering the wrong decimal separators for US$ amounts

Let's talk for a minute about user expectations and magic. A user comes to your tool with certain expectations, and not every user's expectations are the same. You're seeing this first-hand. Culture,...
Matthew's user avatar
  • 2,058
32 votes
Accepted

How to visually format questions/answers to easily follow the story?

Teacher: How to visually format questions/answers to easily follow the story? Student: I think that using "T" as prefix for Teacher and "S" as prefix for Student may help. You may also use the full ...
Adriano Repetti's user avatar
29 votes
Accepted

Are required indicators necessary for radio buttons?

The problem at hand does not seem to be a question of correct asterisk marking rules, or a literal interpretation of metaphor behind the radio button control. Rather, the conflict from your ...
Andreas Mehne's user avatar
28 votes

Users entering the wrong decimal separators for US$ amounts

Show the user what's expected visually and show how the machine interprets the user's input. My contribution to the brainstorm would be: Use a reference to the cheque-form of the old days :) Let ...
Ideogram's user avatar
  • 681
25 votes

Users entering the wrong decimal separators for US$ amounts

You can do whatever you wish basically, as long as you provide a way to verify the input. I would personally dynamically display --next to the input field-- the amount at least partially written out, ...
yo''s user avatar
  • 1,383
22 votes

Splitting credit card number fields into four different inputs

The simplest, if not necessarily the absolute best, solution is a single credit-card field that lets a user input any string of digits and spaces. It should be trivial for the server-side logic to ...
nigel222's user avatar
  • 665
17 votes

DD/MM/YY or DD/MM/YYYY?

Take this example: 01/02/07. At first look, it could be anything. Now, let's make it YYYY: 01/02/2007. Quite a bit of difference, right? This is one of the main reasons for the YYYY format. Very few ...
Sujan Sundareswaran's user avatar
14 votes

How to visually format questions/answers to easily follow the story?

I'm not sure what tone you're going for, but I'd consider going with a chat-style UI, with one person's speech aligned on the left, and the other (perhaps the one with which you'd like your reader to ...
maxathousand's user avatar
  • 19.5k
13 votes

Users entering the wrong decimal separators for US$ amounts

You could create two fields - 1 for dollars and 1 for cents. In this way you don't need any formatting logic and you can strip out any non-alphanumeric characters when you save to a database.
SteveD's user avatar
  • 8,914
10 votes

What is the most readable way to display a U.S. phone number?

I would suggest using the E.123 number unless your audience is purely USA based. That way, us poor internationals don't have to guess about how to call a number. +1 800 555 1234 since then it'll work ...
Paul Hargreaves's user avatar
10 votes

What is the most readable way to display a U.S. phone number?

Although option 1 is used most often, I would argue that the concept of an "area code" is pretty much deprecated by cell phones. Now we simply have 10-digit phone numbers. many areas of the United ...
hymie's user avatar
  • 209
10 votes

DD/MM/YY or DD/MM/YYYY?

When you are not dealing with century old events - it will make perfect sense to use YY instead of YYYY. Even Stackexchange follows the same pattern: "asked Jan 6 '09" MM/DD or DD/MM does change ...
Dipak's user avatar
  • 16.2k
10 votes

DD/MM/YY or DD/MM/YYYY?

Taking into account that this question was asked in the UX section of stackexchange, I would assume that the answer should focus on the user's expectations. I have personally been working in a large ...
not2savvy's user avatar
  • 209
9 votes

What is the most readable way to display a U.S. phone number?

Option 1 has the following characteristics, making it the preferred choice: It's Conventional The Wikipedia page for "National conventions for writing telephone numbers" states: The traditional ...
dennislees's user avatar
  • 11.6k
9 votes

DD/MM/YY or DD/MM/YYYY?

I thought the argument about yyyy rather than yy had been dealt with in the run-up to y2k? There are almost certainly people reading this who will be alive to see 2099 turn to 2100, and there are ...
nigel222's user avatar
  • 665
8 votes

Splitting credit card number fields into four different inputs

Luke Wroblewski, a UX expert with great insights on building efficient forms, answered this question: use a single numeric input field (here’s a video of how this works). As you can see in the video ...
David Regev's user avatar
  • 1,194
8 votes

Tips on number formatting for better readability

Re-sizing elements in this UI may help. Firstly, those first numbers are huge and the ones that follow are way too small. It makes it difficult to read and you can't do so at a simple glance. There ...
UIO's user avatar
  • 2,664
7 votes

Users entering the wrong decimal separators for US$ amounts

Locale is what this question is about. The fact that your users have to handle US dollars, does not mean they will do so in the locale of the 'owner' of this particular currency unit (USA). Date ...
Xano's user avatar
  • 261
7 votes
Accepted

When to move on to the next unit prefix, e.g. 900 kB vs 0.9 MB

Recommendation: Don't change units based on the progress of the download However, it's not uncommon to cut off before that: I've seen e.g. camera manuals say "0.8 MB" rather than "800 ...
musefan's user avatar
  • 7,101
6 votes

Users entering the wrong decimal separators for US$ amounts

The UX solution is to make it error free for the users no matter what format they're used to. Nothing more. Nothing Less. I would recommend that you look into regex type solution: make certain ...
Mayo's user avatar
  • 6,641
6 votes

Why are labels more important than values in forms?

Interesting question! I have always (absentmindedly :P) emphasized the labels and this finally made me look into the matter as I am UX Engineer myself. This is what I could gather and these are ...
Shreyas Tripathy's user avatar
6 votes

Is it ever OK to use italics?

I think it is perfectly fine to use italics. The keys, in my mind, are to (a) use the proper markup and (b) use emphasis appropriately. As far as proper markup, most (but not all...) tools for ...
manassehkatz-Moving 2 Codidact's user avatar
5 votes

When is it appropriate to use masking on an input field?

Remember that a bad user experience is all about Expectation vs Outcome Mismatch So when a user is entering into an input field, he just expects to fill the field, but when it gets masked ...
Saurabh Kumar Suman's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible