I'd like to know all the things that people hate in user interfaces - so that we can have a reference of all the things not to do :)
And anything you especially like in UI's too. Because negativity is a bad thing.
Printable View
I'd like to know all the things that people hate in user interfaces - so that we can have a reference of all the things not to do :)
And anything you especially like in UI's too. Because negativity is a bad thing.
Stuff I hate
1. Small fonts
2. Too many stuff on screen
3. Unorganised
4. No colour
Stuff thats good
1. Easy to navagate
2. Tooltips that give tips
3. Uses Windows theme
But too many different colors is bad too :)Quote:
Originally Posted by Andrew G
Any comments on behaviour ?
Same name on different forms that means different things is bad.
Too many forms open at the same time also not good or
Programs that force you to restart and if you don't they leave that damn huge box that sits in the middle of the screen and won't minimise
I hate:
Popups.
Flash.
Overdone graphics which makes navigation a task to figure out.
<marquee>
<blink>
<frameset>
Pages that don't work in FF.
Screwed up tab orders
Thanks for all the comments so far. Any more?
Personally, I LIKE:
- Consistency in appearance and behaviour, within itself and with the OS
- Easy navigation
- Customisability and extensibility
and I DISLIKE:
- Hidden buttons (things that do things without obviously being buttons)
- Clutter, but at the other end of the spectrum, also over-minimalisation
- Unresponsive or slow UIs
- Fonts that aren't Tahoma :D
Fontsizes that look like they are for the visually handicapped.
Too much crap on a form.
No organization.
Overdone graphics as a ploy to detract from the disfunctional interface.
Forms that to resize but not the controls leaving vast amounts of blank form realestate.
Programs that are slow or irresponsive to the users actions.
Inconsistancy.
Out of order tabbing.
Bad color combinations - ie
http://www.vbforums.com/attachment.p...chmentid=36756
:lol:
christmasy...
One of your own applications, I presume.Quote:
Originally Posted by RobDog888
Yes as i changed the 2 colors to the worst possible combinations to make my point. :D
You sure they weren't "client requirements"? :roflmfao:
I have seen things, so that'd sound believable. :sick:
Nope, just me making a point although maybe you only having 2 eyes lately has distored your view on things. :D
Mmm... distorted. ughghhghghgh :homer:
get your third eye back already..
Whos got mendhak's 3rd eye?
One of the best application I've ever seen. Its quickbooks.
i'm already confused by it..
Where do you start? :confused:
Is that Macromedia Flash or just stuff that flash on the screen?Quote:
Originally Posted by mendhak
Do you people refrain from using MsgBox?
And how about Flat vs 3D controls?
I prefer a style that is (by default) conformant to the user's operating system and active theme - unless you can make a custom-styled GUI that is equally clean and better looking :)
Message boxes - only when you have to. You be a lot friendlier and less obtrusive in giving the same information these days, with labels in appropriate places and things like balloon tooltips, which can replace message boxes that pertain to widget content as the tooltip does not get in the way.
This is your thread PG but I hope you don't mind me asking questions here. :)
When you said Active Theme I am thinking about the Current Theme in XP, am I right? You'll design your app based on the current theme of the user or let your app accomodate according to the theme of the user?
Go for it, it's all about good UI design anyways :)
I design my applications to accomodate the user's theme selection. If they are using XP-Metallic then my application will render in silver. If they are running XP-Homestead, then olive. If they are using XP-Classic or an older version of Windows, then it will render using the classic controls. Basically, it's about run-time flexibility - that includes changing theme on the fly (a broadcast message, WM_SYSCOLORCHANGE or something like that, notifies you of a theme change).
Then again, if you can make a really good looking, clean, usable skin for your app, that's fine too. It depends on what it is. For a media/entertainment application, skinning can work well. For a business application, skinning probably isn't a great idea, you should aim to fit in with the user's OS appearance so that the design isn't distracting from the use of the application.
The image mar_zim linked is a bit of too much clutter: there are too many main level menus and toolbar items.
Anyways, in general, a program I like:
- controls can be tabbed in good order (hey, I use keyboard often!)
- a lot of effort to small details, ie. filling up something automatically if it is possible, on-the-fly prevention of invalid data (instead of showing a messagebox warning when you push ok)...
- keeping things clear and simple looking without leaving out any features
- well organized windows and content so things are easy to find even if you haven't spent time learning it, relating to above
- familiar keyboard shortcuts, following Windows standards and most other programs
- wizards are great for bigger jobs: instead of one big cluttered window, you get a well guided tour to what you want to do
Humm... that is pretty much all general rules I follow in my design. I don't like skinning all that much. About the only program I use skinned is QCD (though its default theme is a perfect example of bad skinning - Soma Black is excellent once you learn how to use it).
I hate -
Buttons
Textboxes
Listboxes
Labels
Forms
RichTextBoxes
Common Dialogs
'Everything else.
Think you could whip me up an application to those standards ?
:lol:
I agreewith most of the people here though, Clutter, bad colour combos, and siorganisation with tab ordering.
I hate it when a program forces a user to interact with it such as a msgbox asking
Are you sure?
then
Are you sure you're sure?
I also hate programs that are scheduled to run (such as backup software) and when they do they bring their form to the front of everything else.
The cheap Backup software I have even gives me a message box telling me that no files needed to be backed up and stays running until I click OK.
Curiously how do you do it when you want to confirm something before actually doing it?Quote:
Originally Posted by moeur
I assume that if the user chose to do something then he really wanted to do it. I suppose for really dangerous acts then a confirmation can be performed, but the act of exiting a program is not in that class.
I've written a lot of programs for people who aren't computer savy and don't like computers. My philosophy is to require them to do as little as possible or they won't use the program.
Especially on repetitive tasks I try to minimize user input by guessing at default data values for them and not putting in confirmation messages.
Webforms
--Cursor Tails
--Music any other place besides the intro (and all 16 bit "ring-tone" music)
--Guestbooks
--Page Counters
Winforms
--Excessive TabControls
--Errors or validation issues only showing up in dialog boxes
--Programs that force full screen on load
--Buttons (or other user events) that will fire without changing the GUI at all (No "Please wait...", "In Progress..." or a bar)
--Basically any design that feels like the program is driving you instead of you driving it.
I let them do it w/o otice and provide "Undo" functionality.Quote:
Originally Posted by dee-u
90% of coders don't know bugger-all about GUI design. That is why QuickBooks sucks a fat one.
A GUI should take up as little overhead as possible, which means you need things like backbuffers and cached data and NOT creating graphics objects at runtime (unless you are doing control arrays which only need to be created at loadtime).
Its fine to do gradients as long as you have an idea of how clock-hungry they are.
Cache everything you can, RAM is cheap, CPU cycles are NOT cheap, remember that.
This and message boxes.Quote:
Originally Posted by demotivater
I hate loath and despise message boxes.
How about message alerts? :D
You've probably seen this, but it's a list on HTML Hell.
Sometimes though some users "accidentally" push buttons (e.g. closing the form before they have saved a record...) or their mouse goes haywire and a confirmations saves the day in such cases...Quote:
Originally Posted by moeur
In cases of saving records what approach do you do to "Undo" it?Quote:
Originally Posted by sevenhalo
What is your alternative for message boxes? Timed form that disappears automatically?Quote:
Originally Posted by Hack
Rollback.Quote:
In cases of saving records what approach do you do to "Undo" it?
You're holding them in transaction? When do you commit then?
Labels... Balloon tips are very good..Quote:
Originally Posted by dee-u
Btw your graphic is coming soon :p
Balloon tips are a great way to alert the user without interfering with their session.
What graphic? Are you making a "IE Lover" userbar? :D
Hmmmnnn... I cant somehow imagine how I would want to show a Balloon tip in the middle of the screen to show some status or something, any screenies?
I am not with the battle of the browsers... :D It's just a software carpenter thingy...Quote:
Originally Posted by RobDog888
I've got no menu's in my app, and it is completely command (button) driven. I started out with nothing but messageboxes, but decided that users don't like to have to center their attention and lose focus on the current form, just to process info. I added a few more textboxes in frames that became visible, and changed the background color to alert the user of a problem. Now, instead of 20 msgboxes, I'm down to maybe one or two.
Baloon tips have to multiple choice possiblities, so I really dislike them. The worst thing about them is that you can't get rid of them until their timer goes out.
If I unplug the network cable, do I really need a baloon to pop up for 5 seconds, every time I open the lid of my laptop? You'd think that clicking the X once should signify that I realized that I unplugged the cable.
I go on-site, and set up WIFI routers, which sometimes require me to use my laptop. This causes that icon to be present until I reboot, which I don't do very often.
/rant off
Kind of like how when in Windows XP you try to enter your password to logon and if you have the CAP lock on it will balloon tip you right next to the password textbox to notify you.Quote:
Originally Posted by dee-u
_HIDEBALLOONTIP ;)Quote:
Originally Posted by dglienna
It's completely the fault of the software developer if it's annoying.
Hmmmnnn... That gives me an idea though I think there are cases that Balloon tips cannot be used as an alternative like when you need options like Yes/No right?
Not really. Replacing message boxes for that requires a re-think of your design.
I like UI's that allow multiple tasks at once. A message box would interrupt all of them.
You could use a little mini-popup thing with the option, that appears over one task and only interrupts that one. That way the user can go on working in other areas at the same time. Sort of like MS Office's Task Pane.
I have always ran into sentiments of "experts" about avoiding using Message Boxes but really haven't found out how to totally rid of them, I've been accustomed to using something like...
VB Code:
If MsgBox("Are you sure you want to save House BL? ", vbQuestion + vbYesNo, "Confirm") = vbYes Then
and
VB Code:
If Len(Trim$(txtPkgCode)) = 0 Then MsgBox "Cannot save record with invalid blank entries. ", vbCritical, "Status" txtPkgCode.SetFocus Exit Sub End If
Though I think the lower example could be replaced by a Balloon Tip on the control...
Without seeing your design I wouldn't be able to suggest a replacement for the message box but for the second you could simply show a balloon tip for the text box. I belive the message is EM_SHOWBALLOONTIP and there are some samples in the Codebank.
Quote:
Originally Posted by penagate
I guess I'd have to blame Microsoft for the Cable Disconnected baloon-tip then.
I'm sure many people hate them, as they tend to be "informational" when you are the one that performed the action to begin with. I'd love to see a Yes/No/Cancel baloon, but if it disappeared after 5 seconds, it would be useless.
you can set the timeout as infinite, so it never disappears until manually dismissed.
I'd like to see one too :)
Lets just cite cases when something that is to be done by the user is irreversible hence they need to be at least prompted if they are sure on what they are doing...Quote:
Originally Posted by penagate
I edited my previous post to comment with a similar one like yours. :)Quote:
Originally Posted by penagate
Whats up with your userbars sig image? austrialans cant hag? :D
Eh ? :confused:Quote:
Originally Posted by RobDog888
I can't even see it. I think the server is down.
And to complement my previous link...
Windows XP Visual Guidelines
Why they had to make it a downloadable EXE that unzips to a bunch of html files, I do not know, but still...
Its been down off and on for the past couple of days causing some page hangs here at vbf. :(
I removed it. The IE one's on Imageshack.
I have been waiting for it to be back online again so I can same that Raiders bar. :( I asked if we could get a special area to house the bars here at VBF. Looks like it may get a :thumb: :D