Tag Info

Hot answers tagged

70

Auto capitalization is impossible. What algoritm would you use to auto capitalize when a lady enters "cléopatra diane de mérode" as her name? You would probably end up with things like: Cléopatra Diane De Mérode Cléopatra diane De mérode The only correct spelling however is "Cléopatra Diane de Mérode" (wikipedia). As you can see, capitalization of ...


61

Option 3 with no intrusive validation. 1 sucks because it's out of the norm. Copy and paste may or may not work. Tabbing to the next field may or may not work. People are good at correcting mistakes and the limited fields mess up their muscle memory. For example I might type 1912 When I meant 192 My fingers will nearly instantaneously correct ...


61

Why don't simply improve the standard numerical keyboard by adding the missing characters ? download bmml source – Wireframes created with Balsamiq Mockups


59

There are a great many assumptions people make about names (also: W3C: Personal names around the world.) Thankfully the W3C have some excellent advice on field design for names, of which the simplest is to use two fields (but not for first/last): Full name [________________] What should we call you? (for example, when we send you mail?) [________________] ...


39

The article Robert Fraser cites is a good one, but it's a decade old. The web has changed somewhat since then. Do you honestly agree with the sentences highlighted in the image below? We must be careful to distinguish between a browser-based experience that is "documenty" (where the BACK button works just fine) and "applicationy" (where the user may need ...


32

No. If you mean something that cancels the current form and takes you back to where you were, the browser's back button is already there. If you mean a "reset"/"clear all" button that clears everything you typed in, then NO, NO, NO! It's way too easy to accidentally click, and adds no value. Either way, here's a must-read article on the subject: ...


31

What is the context of the question the user is answering, and what are the implications? This is the important question that helps guide the appropriateness of "Y" vs. "YES" (or "N" vs. "NO"). In this case you are dealing with a RSA certificate, which is a big deal. Accepting a certificate you don't mean to can have serious implications, so it is important ...


30

Because this behavior is rare and therefore unexpected, it will surprise most novice users, which can cause them to misunderstand how to use the interface, and interfere with usability. (An example of this interference might be if the user fills out the field and presses tab, while you have auto-advanced, and while they think they are typing in the next ...


28

I would suggest no. Treat a person's name - in terms of capitalization, spelling, punctuation and spacing - exactly as the person does. [1] There are a variety of cultures with names that does not use capitalization in all parts of their names. It's true that most traditional English, American, north/central European names are written with ...


28

You say the keyboard is for hexadecimal input. And that's the reason why your second try doesn't feel right! As @steveverrill also noticed in the comments, the numeric order ABCDEF1234567890 is wrong. So if you want to go with a 4x4 layout, you should choose one of these: download bmml source – Wireframes created with Balsamiq Mockups


27

In general users are pretty accurate and fast at entering dates as strings in a text box as long as your validation isn’t unnecessarily fussy and provides decent auto-correction and defaults for the sub-fields (e.g., accepting 2-9-04 as well as 02/09/2004). Calendar controls are great to provide as an option when the user isn’t certain of the date (e.g., for ...


25

Answer: No. Checkboxes vs. Radio Buttons - Nielsen Norman 2004 Radio buttons are used when there is a list of two or more options that are mutually exclusive and the user must select exactly one choice. In other words, clicking a non-selected radio button will deselect whatever other button was previously selected in the list. Checkboxes are used ...


24

Here's a scenario where it might work to your advantage: The user enters their full name in one field. The system reverse concatenates the name as best it can. The field shows the split apart name so the user can verify it. If it's correct, no further action needed. If it's wrong, a little edit button lets them go to the complex form (two fields) and ...


24

In theory the correct answer is no upper limit for name lengths. Allow the user to enter whatever their name is using whatever characters are available to them so that you will never run into a circumstance where someone is prevented from entering their valid real name. In practice that is not possible to implement. There have to be limitations. These ...


21

The major problem with inline placeholder text is after filling out a number of fields, it is difficult or sometimes impossible to determine what the original purpose of that field was. Say for example you are filling out a form and decide to change your input, so you clear it out and then somehow you get sidetracked by a phone call of something else. Is ...


21

This is a tricky interaction, mostly because it has to be super intuitive since the end users are not computer savy. I know it because I´ve had to deal with it in the past :) I had the same problem while working in the UX team at 11870.com (a recomendations website similar to Yelp), this is the way we handled it, might not be the ideal solution but it ...


17

One alternative that I've seen in a number of places is to have two adjacent lists, one with available items and one with selected items. Here's an example from OpenFaces.org that I found with a quick google search:


17

As others have mentioned, Dutch names like mine, even after they've been mangled into something English-like, can still have strange capitalization. If you tried to change my name to "Teneyck" after I entered it, you'd just irritate me. If your clients are unwilling to spell their own names correctly, it's not your job to correct them.


17

To me, this is all about alternatives, providing the "value menu" of things most people would want to say in a tiny comment, in one click. Provided you have made the alternatives, e.g. "click the +1/awesome/like button!" discoverable and easy, I favor a blocking message like: We prefer that comments be longer than 15 characters so they add ...


17

I think it can better to make a visual support for such input, that will allow to enter not only breaks, but also days off. Input can look like this: Clicking on row or cell header (with hour or day) should turn on/off all days or hours. Also you can add popular variants at top of table to select them faster — «24x7», «All days without weekends» etc. ...


16

HumbleBundle.com has a interesting UI for addressing this. They sell a bundle of indie games and let the user choose how much each developer receives, how much to donate to charity and how much to leave as a tip for Humble Bundle.


16

Based on Renaud's idea of extending the standard numeric keypad, but wide instead of tall. Also illustrating that it's OK (even beneficial) to leave space between groups of keys. +--------------------------------------------------+ | | +--------------------------------------------------+ ...


15

A dropdown with 450+ values is extremely unusable on any device, including desktop. But you say that you're only looking for a solution for the basic mobile version, so let's stick to that. Probably the best way to simplify this for the mobile is to have a first screen/popup display the alphabet, then as you tap a letter you drill down to the list of ...


15

as creator of Bootstrap, perhaps I can shed some light on this :). Prepended and appended inputs serve two purposes: Allowing for simple punctuation or units to be paired with an input. For example, if you need to indicate a field is asking for money, use the prepend with a $ sign. Other examples include @ with a username (a la Twitter.com's settings ...


15

Auto-correction shouldn't occur. It takes control away from the user, is often wrong, and is even worse if it's changing the content of the message silently. You cite localization as one of the area in which it behaves badly. It's also the case with old or dead languages, citations, programming languages, medicine or very technical terms... Actually there ...


14

Accept any and all formats typed into one box. As stated by Don Norman: "Compliance: How Microsoft Outlook Does Things Properly Microsoft Office Outlook has done a brilliant job of handling telephone numbers, dates, times, and addresses. Surprise: this is a product that people usually target with complaints, but I intend to heap praise upon them. When ...


14

Unless you can proceed without selecting (leave the field blank) one SD options, I would suggest you go with a radio button. Your layout remains consistent if you are using the same input mechanism for similar tasks. Making it easy for the user to proceed quickly. Radio buttons are faster (easier also in many cases) than using a drop down menu. The ...


14

So, as I was writing a couple of pretty long comments on the other answer, I felt inclined to present it as an answer as well. Following are a couple of considerations not made by the other major designs and mockups implementing these considerations: Mobile virtual keyboards shapes Notice the shape keyboards take on mobile devices on the mockups drawn ...


13

For the 'input lag' part of your question, I still use the rules of thumb found in Nielsen's Usability Engineering: The basic advice regarding response times has been about the same time for many years [Miller 1968; Card et al. 1991]: 0.1 second is about the time limit for having the user feel that the system is reacting instantaneously 1.0 ...


13

I imagine we're at least a couple decades away from the keyboard going away, if not three or four or even more. . When it does go away, the effect will be the opposite of what you imagine. It won't be the keyboard going away that creates new ways to interact with desktop apps. Rather, it will be new ways of interacting with desktop apps that may, some day, ...



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