248
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♦
- 37.1k
144
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 ...
- 2,612
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 ...
- 13.8k
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 ...
- 2,236
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 ...
- 849
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 ...
- 19.3k
54
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 ...
- 906
51
votes
Accepted
For death year, should I use N/A or --- if person still alive?
Well, you can write the predicted year of death based on user research, or you can say "TBD" :).
And more seriously - it would be a good idea to develop two templates for this item, one for dead ...
- 30.5k
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,...
- 2,048
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 ...
- 5,033
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 ...
- 974
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 ...
- 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, ...
- 1,353
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 ...
- 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 ...
15
votes
Accepted
When should bold, italics, and colour be used to draw attention in a sentence?
Highlighting is more relative than absolute
Non-designers often don't realize that the style of highlighting is much less important than the relationship between the highlights and non-highlights.
...
- 40.7k
15
votes
How to display a large quantity of (read-only) fields?
Show all items on a single page in a vertical list
This obviously has limits as it is almost never a good idea to display thousands of items at a time. Though putting a list of a hundred items on a ...
- 15.8k
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 ...
- 19.3k
13
votes
Ideal breaks for long numbers?
4 digits is time-tested chunking for large numbers
3 to 4 digit chunks are easy to read accurately. Perceptually, the eye tends to read words and not letters across a page, and a 3-4 letter word ...
- 40.7k
13
votes
Accepted
What is the best email address format for people with the same first and last name?
Your question seems to assume that email senders have to either remember the email address of the intended recipient, or will have to accurately reverse-engineer the email address of the intended ...
- 3,623
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.
- 8,874
12
votes
Friendly format for phone numbers
There are simply too many rules to validate a phone number input by a user.
1. Phone numbers are ultimately just a string of numeric digits
Here is one example showing how to convert anything a user ...
- 15.8k
10
votes
How to display a large quantity of (read-only) fields?
Observations
It's hard to answer this without a better understanding of what style constraints you're facing, but:
Account information is related, so I'd be inclined to keep it on one page if ...
- 40.7k
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 ...
- 209
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 ...
- 201
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 ...
- 16.1k
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 ...
- 209
9
votes
Accepted
First character of table column name in upper case
In English it is standard practice to capitalize each word in a heading. It looks "wrong" to native English readers. However this is not necessarily the case in other languages.
If your target ...
- 6,611
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 ...
- 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 ...
- 665
Only top scored, non community-wiki answers of a minimum length are eligible