Tag Info

Hot answers tagged

78

Go with checkboxes for consistency Radio buttons usually express mutually exclusive options (EITHER this OR that), so giving an option that includes an item but excludes it at the same time won't be consistent. Contrary to checkboxes it's expected to select exactly 1 item, neither less nor more. Checkboxes are used to select several items (this AND that) ...


39

If the users use the email address to log in into your application, you shouldn't use the word "Username" at all, in any place of your application. In the registration page, they should fill out the "Email" (with a help message to inform they that it will be used to login) and there shouldn't be any "Username" field.


27

Indicating the caps lock is on is a design pattern used for passwords. When the passwords are hidden and every character is only represented by a dot, users might not know they're typing capitals where they shouldn't. It's easy to overlook the fact your caps lock is on. For example, I'm used to typing with ten fingers. While typing my elbows are set quite ...


12

The negative aspect is that you've inadvertently complicated the process. If I signed up and used my preferred secure password then I'm in and done. However with the auto gen password approach I have to get the email, click the link, go back to the email, copy the password "G34-zaopwf792hj" (cause I'm not going to attempt to re-type it) paste it in, then ...


11

Generally, align the left of the field, not the text content: There are several reasons for this: Better alignment. For boxed input elements (i.e. with outlines, borders or shadows), the vertical | edges of the box tend to attract the eye as it scans down the left column so the form will be perceived as more organized if that vertical line is ...


11

Use email Email provides a clearer prompt to the user around what the field is, and how to remember the value. A simple thought experiment illustrates this. Let's take a common situation: You visit a site which you haven't been to for a while. You are presented with one of these login forms: Common scenario: you don't remember your username or ...


9

The checkbox is not dead To your point, a checkbox is perfectly suited to this purpose. In your example, it's not handled with any finesse but it does get the point across. A good UI designer can help you not only "pretty up" your checkbox, but also reduce the friction of interacting with them. The toggle ain't bad either You have to change your thinking ...


8

Beside making the eligible options and combinations thereof explicit, as noted in various other answers, there may be another use case where the radio buttons are preferable: If the options are conceptually independent of each other, and selecting both options just means a mere addition of options, two checkboxes are fine. However, if selecting both options ...


8

No, you should not use CAPTCHA. You should focus on technical ways of solving your problems rather than shifting the technical burden onto your users. As a simple example, you are asking for an email address, so you could validate the email address (which you should do anyway) as a substitute for CAPTCHA. Someone could still write a script to generate ...


7

Well, it was old almost from its own conception. Think about this: how many times will you need to clear ALL info in ALL fields of a form? Now ask anyone you know and you'll probably have a very basic research study that will propably yield an absolute result: NEVER. And like I said, even at the beginnings (well, almost) of web applications this was ...


6

Make verification a separate task Unless this is a high security application I would strongly advise you to completely separate out the validation portion of your sign-in process. Let people use the application without verifying their email or phone number for a limited time. Be sure to make it clear that they need to verify their email and/or phone ...


5

It depends on your situation; a simple one page contact / enquiry form does not need a reset form. Why would you need to reset anything since nothing has been stored yet. If you really need to start over, you could always just refresh the page. However, if you have a form consisting of multiple pages, the filled in fields have most likely been stored in ...


5

Speak the user’s language “Form” and “text editor” are UI terms. They vaguely describe what the controls are but not what they do. Step back from the problem and get into your user’s head. You’ve described one aspect that would drive the decision (document linking). Is that the only reason? If so, you need to find ...


4

Be careful what you're asking the user to provide. The application in this case needs to map things to those legal categories. You may think you're asking "What is your relationship status?", but in this case the application really needs to ask "Which of these legal statuses applies to you?" Because that's what you need to ask, that's what you should ask, ...


4

I would describe this situation as: dynamic nested workflows. Dynamic because you cannot tell ahead of time how deeply nested the workflow will be (user may not create any new objects, or may create multiple carriers and persons). Nested because the workflows for creating a carrier and then a person are nested within each other. The dynamic nesting ...


4

You'll find fields with a little "clear" button in them all over the web. Like this:


4

This example tested well with all types of users It helps if you try it out yourself by clicking the above link but here are the two things that make the X more intuitive and discoverable as a clear button... Only show the X if there is something to clear Place the X inside the input instead of next to it


4

Here is one approach favored by my End Users, have an underlined option stating 'Clear' when the field already has an icon within (calendar in my example). Having an X clear button within the edit field is good, but coloring it red might mean error after the User types in a text. The common theme across apps/web is to use a lighter grey/grey colored X ...


3

Because it's helpful to know the first name and the last name, rather than just the full name Why it can't be done automatically Without asking, a site cannot tell the difference between the following names: Why it matters Sites often want to be able to communicate with customers using different styles, where first and last names are more effective ...


3

I think the feature is very useful for password fields where you cannot see what you are typing and it gives you comfort to know you are typing the intended characters. Of course, most keyboards have a led that is on when you have the caps lock active, but it's nice to be reminded in the context of the form. This is a good practice because most password ...


3

In general, the checkboxes are better. The exception is when all of the below are true: You have enough screen space to handle something like "Both Customer and Item", as well as having three radio buttons instead of two checkboxes You are targeting users who are unfamiliar with web interfaces such that they won't naturally just click on both checkboxes, ...


3

Use the terms "Login" and "Password", and add a hint to the login field stating it can be "username or email". If you for example check this german real estate site, they have one field for everything (location, city, zip, street, some id) with a hint explaining it: http://www.immobilienscout24.de/


2

As everyone has already said, it's usually required only by the backend. And yes, your colleague was right, users WILL get confused and think that you are asking for two different addresses if you word the lines like this: "Address 1" "Address 2" A better way to word the fields is like this: "Address" "Apartment, Suite, Unit, Etc. (Optional)" This way ...


2

The modal pattern is great for quick low friction input. It allows you to ask for information without leaving the context of the current task or activity. If your form is complex (lots of inputs) and/or the from does not request input that is directly related to the current view use a stand alone form for your input.


2

The problem here as you correctly mentioned is that users are confused. Its because they might confuse with booking the ticket rather than checking the availability of the flights. Most of the use cases are departure and return or day of flight. Your start date and end date is confused with the start of journey and return. Proper labeling is required to ...


2

It seems like your interface layout is going to be very similar to most booking sites in regards to the calendar selection. From what you've described it sounds like you just need to label and communicate clearly to the user that the dates being selected will result in a broad search, not an exact match. The word "scan" can be a little misleading. To better ...


2

Marriage has both societal and legal connotations. If you're only interested in the legal connotations, then you need to be explicit in that in both the questions and the answers.


2

I think the key question is, do you need to verify the email address or not? I would only send an email for verification purposes or just a welcome message. If you really want to eliminate fields to fill in, you could start with name, emailadress and password. Then ask their other details in a later stage.


2

I believe it is wrong to give a warning that the caps lock is on because after all if a user already typed in his email/username before entering his password he probably knew its on. Additionally some people have passwords with many capital letters in them so they use the caps lock instead of the shift key. Its not your responsibility to tell a user to ...


2

I would recommend two spinners with "From" and "To" labels (or "between"/"and")- this allows for good keyboard control, accessibility, tabbing/form navigation, but also preserves the ability for the user to enter arbitrary values unlike a dropdown: download bmml source – Wireframes created with Balsamiq Mockups



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