Tag Info

New answers tagged

2

Conscious Decision IF the main idea here is to force the user to make a conscious decision to provide or not provide a phone number then maybe you could integrate a radio button group into the control. Radio Buttons The first radio button could live alongside the text box for the phone number. Selecting this one would mean they then have to provide some ...


0

Firstly, put an '*' and some text indicating the field is compulsory and you'll have less need to present people with this unconventional validation. However...only make the field compulsory if (as mentioned be others) there is a strong business case for it. The other issue with your example is that some users may skip the phone number hoping they don't ...


0

This is very confusing I have to say, reminds me of the fuzzy logic. Well fuzzy logic is a nightmare for the user, as he would like the system to keep it simple. Also, the user probably saw one or two forms in his life, I guess not a single one behaved as you suggest above. Bottom line, there is no semi-required like there is no semi-pregnant.


2

Are you sure that you're sure? This is the question you ask your users with this type of strategy. Business goals From a business perspective the thinking is: Required field - we must have it. Optional field - provide at will. Users The way optional fields are seen by users is: I can either provide it or not. If the user is aware of what is ...


1

While I've seen it before, I much prefer the yellow highlighting on fields like that. We tend to go green and red for traffic lights, if you should do it, but don't have to yellow fits perfectly.


1

having a persistent message at top for the error message would rather than inline validation for the field, as it is off 20 fields collating error message at top would work and you can indicate the All Fields Required on to the top left corner. Also the progress bar context here for few of the fields that too on a single page is not required as such.


2

1. Is it OK to resize the dialog to accommodate changed content? Yes it is nowadays, providing it doesn't cause the window to scroll offscreen. There are lots of ways to do validation notices, but the approach you've chosen (notify below the field, red, left-aligned) is a very well tested and classic approach so it's a safe choice. The main downside to ...


0

I try not to ask for anything unless I need it. It should be clear to the user why providing me what I'm asking for will help them. There are a few cases where something is useful to the user yet not required to get the job done such as providing a Description. I don't usually find it necessary to put (optional) by these fields because a user isn't harmed ...


0

If you really, really, really have to use a tree view with hundreds of nodes, then it needs to be just that: a very basic tree view and absolutely nothing more. Sometimes this situation is unavoidable. A tree view is often used for expert users who want to be able to navigate a complex hierarchy quickly, without waiting for page reloads. In this ...


0

I may not solve your problem with the following approach, but I am fairly certain that the current implementation is overwhelming to the user. It adds a lot of performance issues. It is also hard to comprehend if I want to have a look at more data in one go. Let us start with 80:20 rule. When I design something, I generally make sure that my solutions ...


1

The idea of showing the item in your list is good - having it disappear or not labeled as "Discontinued" would be jarring and confusing. Using the disabled style sounds fine. The product selector should be easily found from looking at the discontinued line item, and the discontinued item shouldn't be listed in the product selector.


1

In all other cases, when the product is discontinued, do you plan to show it in the selector? I would advise against it. You are talking about a case where use has an un-submitted order of a product that is discontinued. I am assuming the errors are shown to the user when user goes to interact with that particular order (either save/submit it). I would go ...


0

Show error messages before the user even started filling the form can be misleading since the user haven't started to fill the form yet. From what I've seen in common forms, the error messages appear usually when the system recognizes an error while the user try to submit. This can also be misleading, especially when there is a large form and the error ...


3

One relevant study that springs to mind is described by Luke Wroblewski in Inline Validation in Web Forms. It found that validating inputs prematurely can be harmful and that validating fields after input helps users to complete forms more quickly and accurately. To better understand when to show inline validation messages, we tested a few variations ...


1

Your suggesting would be poor UX, and poor business logic. By your logic every address that is of the form me@mydomain.com would be rejected because someone somewhere used a me@.... email address. There are many common names before the @ in email addresses, and trying to exclude me for example because there was some other iCloud user with the email ...



Top 50 recent answers are included