We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

127

Software development IDEs have some of the most complicated settings pages I've ever seen, and IntelliJ IDEA does a great job with discoverability. Not only do they offer a search to narrow down the left "tree" to matching pages, they also have a special highlighting effect for matching options. This is similar to your Chrome example, but even better since ...


72

When a user is about to take an action that may not be easily reversible, it is imperative that the interface give them enough information to: Make the correct decision on what they want to do. Make it very clear how to make that happen. In Windows 7 the "Copy File" dialog gives you plenty of information to help you compare the two files using meta data ...


69

While Charles's Answer shows some great UIs, I wanted to add the UX that Directory Opus uses for the same action, which I find very good as well. Simple on the surface with advanced options tucked away after a click. . Clicking on the Dropdowns results in these options: As you can see it also provides shortcuts for the advanced operations making it easy ...


65

You could use an accordion. Here's an example of one I've used before:


35

Yes - underhanded, but this is not a problem reserved for the web - it's long been an issue for print too. A couple of years ago, the EU banned pre-ticked boxes on shopping websites in order to prevent such issues as unintentional purchase of insurance or optional extras when purchasing plane tickets, for example. The legislation does appear to revolve ...


24

I'm the author of WinSCP and I've found this "question" really inspiring. Thanks. This is my (kind of) "answer". Improvements I've done (see also the screenshot below): Inspired by the @Vijay's answer (and Directory Opus), I have merged similar buttons into one with a drop down menu. So now there are only 4 buttons, Yes (with Newer Only and Yes to All in ...


18

Root Cause: Implementation Driving UI The whole idea of a single consolidated Options dialog seems to be a consequence of programs having configuration files. The Options function would read the configuration file, present it to the user in a dialog for editing, then save the changes back the configuration file. Perhaps some other programs do the same thing,...


16

That is one of the best examples of an interface designed by engineers for engineers :) I would suggest the following improvements: Some of the options should be moved to an advanced section, which is selectable for people that know that they want advanced features. Related options could be grouped together to make it easier to scan. The buttons should not ...


13

I'm not sure you should rely on a copy change alone (or even if it worked, it may not be worth the added confusion - see @joe larson's answer). You might try instead calling out an explicit warning: download bmml source – Wireframes created with Balsamiq Mockups


12

Could you combine all 3 in a singe field with the label "Phone Number, Email or Name". Other than that I can only suggest using text to describe what the user should do - "Please fill in ONE of the following:" for example. download bmml source – Wireframes created with Balsamiq Mockups


11

It could be useful in the following circumstances: When the user's native language isn't English, but they are more familiar with English labels than the native equivalents. For users who need to switch keyboards (and auto-complete dictionary) using both their native language and English (or another secondary language). For users that give their old phones ...


11

Usually the option in capitals is the default. The default will be used if Enter is pressed.


8

download bmml source – Wireframes created with Balsamiq Mockups If you can have one and only one identification method, then let them select which they want to use via a group of 3 radio buttons and once they select one make the label and input for that identification method visible or have them disabled until selected via a radio button. The ...


8

I think FileZilla does a good job of this. And they give you options to never ask again when overwriting - either in the current queue of transfers ('apply to current queue only'), or for the entire FTP session (just 'always use this action' selected). If they were to add any more options though, I reckon a drop down list would be in order for the 'action' ...


8

The select field on your screenshot might not be the best solution for selecting the payment period. As a user I don't get a good experience in comparing the alternatives and probably I won't notice that there's an alternative to the very prominent designed orange 49.90/month offer. The problem here is that 50$ per month is a lot if the user wants to use ...


8

For a simple A, B, and A + B selection you shouldn't need to get too fancy and radio buttons are a good approach: They are an instantly recognized widget for 1-of-N choices. They spell out the options clearly. Users need only 1 click to select any option (vs up to 2 for checkboxes). Radio buttons and checkboxes are both small controls so the added click ...


8

I posted a related question recently as I have been struggling with a similar problem. From what I have mustered there is no clear and clean cut solution, as these kinds of "options" are often very contextual. This article briefly covers and provides some well known examples. However, I still feel that there is much to be done in terms of design solutions ...


7

In this situation, you're correct to reject the 7+/- approach. Really, the answer is that too much choice results in no decision being made. This is a variety on the Analysis Paralysis. Analysis Paralysis refers to over-analyzing (or over-thinking) a situation, or citing sources, so that a decision or action is never taken, in effect paralyzing the ...


7

Wouldn't it be better to collect statistics for, let's say, a week? Then you could take the decision (or help someone who will decided) based on the behavior of the real users of the site. You can find, for example, that even when the company pays something for the person, that person has a specific/limited budget to spend, and by seeing trainings that fit ...


6

As a layout I agree that the above (edgarator) is more clear than your current options. From a UI/UX crossover point of view I have worked with addition field layed out like this quite a few times and have found that it is better to design the field in a way which makes the user feel like they're adding in a new record directly to the HTML table rather than ...


6

I recommend reading this excellent case study of how Evernote got its customers to pay for its service which was initally free. To quote the article But according to one hugely successful startup which operates under the Freemium model, Evernote, converting free to paid is all about engagement. "The easiest way to get a million people to pay for ...


6

Is this the right feedback? Not much to go on. You may need to test and probe more about what’s really bothering users. Is it really a strictly aesthetic problem? And does this user feedback come from users simply viewing the prototype or actually using it in a task? You can get very different reactions depending on how you’re testing. For example, users ...


5

I usually prefer users to see just what they need to see (the simplest the better), and only give them deeper options when they need them. Eyal's solution is very good, but if we are talking about 50 companies then it would be a bit overcrowded. Another option for me would be: Companies > (combo) All -link- Show advanced options OK And when you ...


5

How can you Add Detail if there is displayed short version of record? User don't see which details are already entered and which could be added. So Add Detail should be inside full record view. View in your case is not necessary. And Delete could be group operation, like in email clients. So you can simplify your table by removing Actions column. View ...


5

Grouping can be improved by drawing a line between "Configuration" and "Preferences". Everything that the user has to configure to get your app running should go to "Configuration". Everything optional, which can actually be a matter of preference, should go to "Preferences". For example, I hardly have a "preference" for the default printer (it has to be the ...


5

The solution is pretty simple. When someone completes checking three checkboxes, disable all non-selected checkboxes. If someone clicks on a disabled checkbox, show an alert to the user that already 3 options are selected. However, you can make the design more intuitive by having some progress element. This is the state when the user has checked only two ...


4

Hi and congratulations on caring about making things easier for users! My first suggestion is to ask users. Do a paper or post-it prototype (Wikipedia: paper prototyping) and go ask five people. (http://www.useit.com/alertbox/20000319.html) Second: it is tempting to think that users will be comfortable when all screens have the same mechanism. You are ...


4

If you don't plan on implementing a down vote, I think it would look strange to only have, for example, an arrow pointing up. Or a plus symbol. Likes are accumulative, while voting needs at least two options (otherwise it's not a vote), and some associations might be quite strong, like up/down, yes/no, plus/minus. I would probably feel something is missing ...


4

Have you considered renaming options to "Bank transfer (takes a couple of days)" and "Instant payment (PayPal)" or something similar? I noticed that your option names are very similar to each other and that might confuse the customers.


4

One big issue here is a lack of hierarchy, all of the buttons are given equal weight on one wide line, which ends up being overpowering at first glance. The user wastes mental energy scanning all available actions because he/she assumes that all choices are equally important. I believe this dialog box should be customized, with obviously the 2 big buttons (...


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