Tag Info

Jumping in with an answer because I've seen a really nice example of this in the wild. Hargreaves Lansdown is a UK financial institution, and here's how they do it: The idea of giving context to a user hadn't occurred to me before I saw this. In practice, I find it far faster and easier to input a password when I can see how far the requested characters ...

If any service can validate what the n-th character of your password is, it means that they are storing your password in an insecure format. No service should ever know what your password is, they should only be able to say whether your password authenticates or not. So you shouldn't ever ask for the n-th character of a password, and you shouldn't ever be ...

HSBC uses a combination of a username, password, and security key. In this implementation, you first enter your username. Next, you are prompted to enter your password and three random characters from your security key: download bmml source – Wireframes created with Balsamiq Mockups The benefit of this approach is that the password does ...

You should ask for the entire password, not just because it is more secure, but because users entire passwords by muscle memory, especially passwords made up of arbitrary characters, or defined by movements across the keyboard. This makes it hard for users to recall characters in specific positions.

What you are describing is a Combobox and has been in use for as long as I can think about GUIs. The concept has gained new momentum in the web with the further development of dynamic elements and web apps – most notably google's search box with it's suggestions-as-you-type. Chrome's "Omnibar" is, basically, the same thing: It's a text field you can type in ...

I can't say I know of any research into this, but for me this would be a no go. It just isn't intuitive enough for the user. Perhaps a better solution would be to present the user with a drop-down in the first instance, if then the user cannot select an appropriate option, reveal an input field giving the user the ability to manually enter the relevant ...

Whether or not you need to be able to cancel an action (edit or insert) is dependent on the consequences of the action. Does adding or editing an item have immediate consequences for the user (i.e., is business logic executed, etc.)? If not, it may be OK to leave out the cancellation option - the user can always delete the item, change the value, or go ...

In one of the heavy applications in my company I have developed almost identical UI as you have provided. There is only one button that I provide (Add a group) which immediately shows an input field without a confirmation. To cancel, a user may press an Esc key. To save, just like you said, press an Enter key or remove focus from the input field. To ...

My solution would be to complete the login process in two steps. Ask the user for the username, which if correct Generate the password field asking for only password on the next screen.

The best way in my experience is to do at least the following: The text should be high contrast, for example black on white (preferred) or white on black depending on your design. The text should be visually distinct from labels and other non-editable fields in your application. If your application uses a mouse, ensure that the cursor changes to the I-beam ...

This isn't answering your question with research and what not but how about something like this? http://jqueryui.com/autocomplete/#combobox Similar but filters down and could also accept the users unique input.