The thing is that none of the options can be removed (those who can have already been), and that they must all be visible at a glance (i.e. no tabs allowed) Edit : I've added a comment explaining why tabs are not an option in my specific project.
I've tried to use colors, to add icons, but it just added to the overall feeling that someone had just dropped controls randomly using Visual Studio Form designer during a summer internship.
How can I make this dialog
more user-friendly less horrifying without deleting features ?
Edit : The GUI example I took has a lot of obvious design flaws (see those answers 1 2), but even after fixing those (which I've done on the software I'm working on), the dialog still looks pretty ugly.
Below is another example (credit). Controls are (almost) lined up correctly, appropriate controls are used, etc, but the overall result still looks terrible :
Any math approaches to state management of complex objects?
Theory of Game Interface Design [closed]
Blackberry Storm - focus issue on bitmap field
A good starting point would be to equal the alignments and control distances to increase overall symmetry with the ultimate goal to reduce visual clutter..
BlackBerry Storm - focus does not comes on focussable fields added after scrollable list field
automate user interface test
- The group boxes "Special" and "Running options" should have equal height.
- The distances between the four buttons "Save settings" and "Exit" should be equal.
- All buttons should have the same height, if possible avoid word wrapping.
- Use the same height for all single-line edit boxes.
- The quota label and its text field should be at the same baseline.
- The distance between a group box caption and its first control should be equal (compare "Running options" to "Retrieval options")
- Increase the distance between the controls in general, i.e.
What operating system and UI toolkit is this?
make the form look less dense.
Controlling video playback (play, pause, forward, seekbar) on BlackBerry
- Use the same captions/names for the same things.
What is the opposite of JAXB? i.e. generating XML FROM classes?
For example, you use "Append to logfile" but "Overwrite Logfile
- Use the same character case, sometimes it's "Only the first one", "Every Single Word" and sometimes "it is Camel-cased".
Decide on one scheme and use it consequently (Sentence case and Title case are the most common)
- Don't try to be cool, "Go 2 background" doesn't look very professional.
- Avoid controls with unreadable shortcuts or no content at all.
It doesn't help if the user has to stop on every control and think: "What does this thing do?"
- Try making the group boxes more symmetric, possibly be re-positioning them and use the same height.
If necessary use two columns of checkboxes, that would still look better than uneven group boxes.
- Unless it's absolutly necessary, remove the horizontal scroll bars from the two multiline edit boxes
- Get rid of the "Clear" buttons.
For the list box on the buttom left you have to provide some other way to delete items, perhaps make this into a multine text box, too.
- Try replacing the checkbox collection with a checkable list box or a property grid.
The less different lines reach the boundary, the better.
(Because correctly aligned controls produce more incident (-> less unique visible) lines). On the use of colors and icons:. Simply adding icons and colors doesn't solve the fundamental problems such forms have.
They all suffer from being overloaded with controls and adding even more only worsens the problem, because they just add more visual noise, but don't provide any more visual cues.
You think you're saving space by making things smaller, and putting them closer together, but it's a false economy because your eyes have to work harder to differentiate elements from eachother.
Think about writing a computer vision program that had to OCR those interfaces, and the challenges you'd have just figuring out which element was which, let alone what the type says.. Regardless of what your programmer efficiency instincts might say..
it's okay to put space between your elements, and hell, it's okay to even have large amounts of completely "wasted" space too.
. have a look at this . There's a clear boundary between the flower and its background.
The shallow depth of field of the photography gives a clear contrast, and allows you to very rapidly construct a mental sillouette.
. . what's going on in this image? There's too much detail, and it's all over the place.. have a look here. http://www.papress.com/thinkingwithtype/text/line%5Fspacing.htm. . think about what the line spacing is doing to your ability to distinguish words from eachother.
What's it doing to the visual sense of clutteredness?. You can see from the type example that you don't have to give up much in terms of space efficiency to see massive gains in visual appearance..
Both these controls help you pack lots of information in very small space, and still give you full control over their visualization (you can add descriptions, tooltips, etc.).
The thing is that none of the options can be removed (those who can have already been), and that they must all be visible at a glance (i.e.Sigh.
no tabs allowed).
I would argue that, because everything is visible at a glance, they practically become invisible in a sea of controls.. That being said, the ff (yes another list) are my suggestions:.
- To reduce clutter, make the overall form bigger, and all controls more widely spaced apart in all directions
- Standardize the height of the controls, e.g., textboxes must all have same height, buttons all have same height, etc
- Align labels with text boxes more consistently
- Make the layout flow down instead: 1 column, with each group having the same width as all other groups
- Set all group box names in bold to make them stand out
- Put all those "wGetStart.bat" commands in a group of its own
Heavy 3-D controls in large numbers are detrimental to the aesthetics and usability of a window.
Consider editing their properties to flatten and lighten the controls’ appearance, using something I call “compact presentation.” In addition to removing the ugliness and distraction of heavy borders and backgrounds, this also allows controls to be placed closer together, freeing white space for grouping them without resorting cluttering lines and frames.. It looks something like this (after also fixing alignment and redundancy along with a little re-arrangement of groups):. .
If they can be minimised/unpinned when not needed, then they can also free up valuable screen estate and unclutter the UI.
See VisualStudio itself for a nice implementation.
- make it bigger, this allows a more structured grouping by reducing the space constraint on each group
- add some structure by grouping options that the user might want to combine at the same time
- add meaningful headers (might require the previous item).
"special", "running options", "retrieval options" don't really convey any useful information.
- make sure that only options that can be combines randomly are checkboxes (for example are "no info", "all info", "some info" really completely independent options? Same for "append to logfile", "overwrite logfile").
- use appropriate controls (spinner for number entry, file selection dialog for files, radio buttons for mutually exclusive items, ...)
- deactivate controls that make no sense with current configuration (for example custom directory text field).
- move all actions to a single place
- hide the scrollbars unless they are actually needed (i.e.
reduce visual clutter)
- be more consistent (why is it "running options" and "retrieval options" but not "special options"?)
File, Edit, Tools, Help.
And also a button bar too?.
Even if everything must be visible, I think that some functions are more important than others.
Also, make a clear separation between functions that apply to the domain (e.g., Start wGetStart.bat) and functions that apply to the software (e.g., Save settings).. Second, organize the layout according to this hierarchy: most essential to the top and to the left.. Third, let your design breathe.
Space is fundamental for defining content..
Yes, it's ugly, and yes, I would be personally embarrassed to admit that I designed an interface that looks like that.
. However, this window only produces a negative reaction the first few times you look at it.
Once a user has used this form a couple of times, they will stop seeing it as a random collection of controls and instead start perceiving it as an interface that lets them see every piece of information that they require at a glance and that lets them do everything they need to do with a few mouse clicks.. It's a dialog for setting a bunch of options, and it's probably perfectly functional and not a big deal at all for your users.
You could put a lot of work into some weird, fancy-schmantsy replacement UI that might impress the StackOverflow code-noscenti, but we don't pay your salary.. Now, the second window - that's a piece of crap..
While I have never dealt with that segment of the market I have often dealt with executives who need very specific information to run their businesses and the first cut of the application almost always looked like what you have displayed.. The original solution back in the day was to build a very light custom interface for each user of the application focusing on only the information relevant to that person.
More recently the move has been toward making the interface customizable by the end user.. Chances are that none of your users are using all of the information presented to them.
Each of them is using only a small subset.
But each user is using a different subset.
Try building the software so that each user can display only the information that they will be basing their decisions on..
So you can have a keyboard accelerator, menu option, detachable panel, tabbed area ...
. So this existing form could be the main, default interface (albeit improved with some of the other good design tips in other answers), but why not create an "expert" panel which can be a lot neater and try to work your users on to that, and away from this old "do everything" blotter.
Figure out what users want to do most frequently and most consistently with your application and default to that.. You should consider a wizard for this UI.
Guide the user through a set of screens for the first use.
And move many of these features as configurable options preferences.
. Usability is not merely aesthetics IMHO.
It is about making clear what the app is intending to do.
I would refactor this app to provide shortcuts to common options patterns.
If 90% of the time I am going to use a specific configuration of options why do I need to see every feature enumerated in the UI 100% of the time? It is just unnecessary clutter.
Sensible defaults powerful configuration that is the goal.
You don't have to sacrifice features, in a sense not making me think is a feature, perhaps the most important feature.
. With respect to your specific app I would rework it with two basic screens a clean default screen and an advanced screen.
Add the ability to create shortcuts to common configuration sets on the default screen.
A simple button that maps to a specific configuration set and asks me for a url.
And if the user needs to tweak an option present them with the advanced screen but treat it as preference configuration screen that saves the preference out to a shortcut button.
If I want to use the configuration more than once let me save it as a custom bookmark or option on the defaults screen.. This is one of the things OS X does really well.
There is a lot of power and customizability in OS X, "hidden features" if you will.
But the OS defaults to sensible and straight forward options.
Provide tools to the power users but don't clutter the system for the first time or casual user.
This is not sacrificing functionality, it is effectively organizing functionality.. That is my first suggestion.
But if absolutely don't want to hide options, I would make this a long scrollable vertical list organized in clear steps with explanation for each step:. Step 1: Provide URL __________. Step 2: Configure Hosts _________. Step 3: Configure Retrieval Options: . () option. () option. () option. () option. And so on.... At each step provide some context to the meaning of the configuration options.. The advantage to this is that you can clean up the UI aesthetically and provide useful configuration hints.
I don't know what "Empty wGetStart.bat" means.
I presume this empties a batch file of some sort.
Provide me an explanation so that I know whether I want to click that button or not.
And then let me hide explanations under a collapsible menu if I use the interface regularly.. My two cents..
Most of the time, the user just picks a named style.
When the scary stuff is necessary, a click of an 'Advanced' button can grow the form to show all the options at a glance, to allow a few to be overridden, or to allow new named styles to be defined.. Obviously, a major advantage is that if there are a few particular configurations that are regularly used, it's trivial to switch between them and there's very little risk of accidentally setting one of the options wrong.. Another option - don't have all your options on display, use tabs or a wizard or whatever.
Instead, have a text list of all options currently set (or all options in non-default states or whatever) to get the at-a-glance visibility.. These could be combined, so that your summary display says something like "like <style name>, except for ...", based on the style that's least different to the current options..
Does that mean they have to see all the checkboxes and frames and scrollbars at once, or just the information?. For example, instead of having a multitude of checkboxes for option 1, option 2, option 3, etc, in the main GUI, only show the selected options and give the user a way to open a configuration window when they need to change something.. Instead of this:.
+- Feature Set X - + | | | [x] option 1 | | [x] option 2 | | [ ] option 3 | | [x] option 4 | | | +------------------+
This lets the users see all the selected options without having to take up valuable real estate for all of the widgets necessary to change the values.. (apologies if the ascii art doesn't appear right -- it looks right in a fixed font :-\ ).
feature set x: option 1, option 2, option 4 [configure...]
Managing UI Complexity by Brandon Walkin..
I would add the ability to click and drag to change the number(if your users are used to that I know several 3d packages that do it so it wouldn't be uncommon in relation to the example).
You can change check boxes to buttons with backgrounds that change color or stay depressed when clicked as another option to reduce visual clutter.. In the right hand side box there are two or three separate functions mixed together that very well could get their own tab.
When you are working with an object's color and texture you aren't going to be changing its size and view aspect ratio so having them right there means they are in the way.
At the very list they need to be rearranged to be in some sort of logical order right now they are all over the place.
Texture and color(things that effect color) should be together.
Position rotation and view(things that effect shape\size) should be together..
If you can't post screenshots, then the best advice I can give is to hire a designer to help you work on the graphical end of your application; otherwise all you will get are general guidelines here.
. Some things that might have not been discussed:.
- Think about the users of your applications and the systems that they run.
I believe that most stock traders will have large dual monitor setups, so you can probably make your dialog larger and add space between your controls to make it look less cluttered.
You should research your audience and see what they use.
- Are you using the best controls for the job? In the first screenshot you posted I noticed a few controls that could be changed:. a.
Under "Running Options" I see three checkbox options called All Info, No Info, Some Info.
If only one can be selected at a time then maybe they could be changed into a drop down selection menu.
Also under the same "Running Options" there is Append Logfile, Overwrite Logfile, which again you can convert to a drop down menu since you can select only one.. b.
The two text fields where you can put in hosts, can probably be combined into one gridview with three columns.
The first column is the host, the second is a checkbox for Accept, and the third is a checkbox for Reject..