|
It's Tuesday and I was avoiding actual work 
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
|
|
Foothill wrote: Lead the eyes
My sole opinion: That is The pillar of good UI design.
|
|
|
|
|
Other good rules:
Default action should never be destructive. (You wouldn't believe how may times I was swearing out loud when switching from an editor asking at exit "You have unsaved files. Do you want to save them?" to one who asked "You have unsaved files. Do you really want to exit without save?" Default: Yes, in both editors!)
Normal termination is at the end of the page - lower right corner (in a left-to-right culture). The lower right is NOT the place for e.g. a "Cancel" button! This rule was firmly established in early Windows UI, but nowadays you may see the "OK" or "Done" button more or less anywhere, and the lower right button may be anything.
Avoid, as far as possible, switching between keyboard / mouse / ... So, provide keyboard shortcuts and a thoroughly planned tab key navigation sequence. (And set intial focus to the field the user will fill in first.) Make use of the mouse keys, menus and other graphic controls so that you can do "everything" with the mouse until text input is required.
Make sure that your UI can handle zooming. This is especially important if you aim at a user group including persons above 30 years of age.
Make at least a minimum of "Universal Access" adaptations. E.g. smear some grease on a pair of glasses and see if you can still read the screen (there is a popular trend in hairline fonts that is very hard to read with smeared glasses). Do not require super-precise mouse navigation. Be aware of differerent kinds of color blindness.
|
|
|
|
|
My favorite design principals.
Keep in mind that someone may have to look at that page/application all day long.
Have pity on them: no more content than necessary; larger fonts and pleasant contrast.
Get the work-flow from someone who's using it. Locate things, and certainly tab order, to take into account how they think makes sense. Usually, they're right, and even if they're not, they'll feel comfortable.
Although I did have to build an application with intense context sensitivity and remapping of component values, ideally, you keep the use of each component to a single purpose. This reduces the learning curve. That doesn't mean, for example, that a picklist's contents can't vary. What it means is that the implications of what you're picking should be obvious and consistent for that particular control.
A few well-thought-out tool-tips where essential. If you did the work correctly they'll not be needed.
Other opinions vary
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
As already noted, there is a (free) ux guide from Microsoft, sporting over 600 pages worth of information. It is not just guidelines, it contains argumentation on why they do stuff that way. Download it, print it, and learn to dream it - a great way to end those annoying discussions.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: here is a (free) ux guide from Microsoft, sporting over 600 pages worth of information.
ummm, didn't microsoft give us metro (or whatever they're calling it today ... but maybe not tomorrow).
Didn't they give us the new Windows 10 looks - plural because not consistent.
jokes aside: that free guide from Microsoft, don't waste you're bloody time, 600 pages of sh*t.
Microsoft have some pretty good software but they've never lead in design, never.
case in point: compare the UX of apple to Microsoft past and present:
... which one looks better?
... no, make that which one has always looked better.
Sin tack
the any key okay
|
|
|
|
|
Perhaps you should try reading it before you comment.
The UX Guide does not only document some good ideas, it explains the reasoning. Does not mean that the Office-team adheres to it, as some dimwits NEED a new UI to accept it as a "new" product.
I support Microsoft in both decisions.
Lopatir wrote: case in point: compare the UX of apple to Microsoft past and present:
... which one looks better?
UX design has nothing to do with "looking better". And yes, the market has decided with their wallets - the fruit was never to be taken serious.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Skimmed it some time ago, lot of typical boiler plate basic info but really nothing you wouldn't get from the idiots guide (in way less words.)
Their portfolio is out there for all to see, and when it comes to UX it [no pun] 'aint pretty!
Better to ask somebody that demonstrates actual ability rather then paraphrase the obvious.
Beauty queens, six year old kids and clowns all know how to put on make up.
Which would you ask for advice on making yourself look good?
Sin tack
the any key okay
|
|
|
|
|
Like I said, try reading it 
Lopatir wrote: Beauty queens, six year old kids and clowns all know how to put on make up.
Which would you ask for advice on making yourself look good?
UX design is not about "looking good".
That is exactly what went wrong - people who assumed they knew better and who imagined they could create something "cooler" looking. UX design is about discoverability, usability; it is the difference between the old DOS 5.x manual and the manual that came with Windows 95 (hint: none).
Terms like "pretty" are not applicable in UX design; and from a developer I would not accept a marketing-like approach 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
I couldn't agree more. I had a customer who was like that. They gave us a mountain of specifications and rules and then we found they don't actually follow them but we had to.
|
|
|
|
|
{facepalm}
Now for a rant as I am getting pissed off with trying to use an email template to look even remotely readable in android-gmail-exchange, which for stupid reasons looks different then using a gmail account in the gmail app.
maybe I asked this wrong -
I am not after new guidelines, I am interested in if there EXISTS already something that suggest a basic: Where placed - How it looks - What is its function.
Some generic or principle instead of specific guidelines for a platform/device/language
If I know what I was looking for, I would google it and find something. Hench why maybe something does exist but uses different words, thus am unable to find.
|
|
|
|
|
I'd still recommend printing the ux-guide and reading the entire thing.
Though it is aiming at the Windows-platform, the ideas are universal. If you see a button, you know you can click it. You also "know" that you cannot edit text in a label, only in a textbox. Those would be rather basic principles, right?
Gmail is not your app, so you might not have full control on how the mails are rendered.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
Dunno; looks like it is just a small part of the guide.
http://www.glyfx.com/useruploads/files/UXGuide.pdf
Sorry, not clickable link as the websites editor goes nuts when pasting a PDF-link.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
It all depends on the stupidity intelligence of your anticipated audience. 
Just look at the difference between Republican and Democratic websites.
Marc
Latest Article - Create a Dockerized Python Fiddle Web App
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Just for the hell of it, I opened the DNC's and RNC's official websites.
I'll keep my personal judgemental comments to myself - it's not about them competing for me.
It's about, really, both pandering to those already committed.
For that reason, I will concur with your comment!
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
In addition to what Foothill said, think about workflow. Make the app cater around that, as a whole. Quite literally, the user's interaction with the app should flow like a river in a cohesive design. If you have them jumping all over the place it'll be harder to use. Also, read up on UX designs and remember, less is more. For a business app that people use every day, don't add the extra flashy stuff. It gets old after the novelty wears off. If it's something that's meant to be seen only once or twice then by add means add the flashy stuff however.
Jeremy Falcon
|
|
|
|
|
An addendum: Respect the domain specific, professional terminology. Nothing is as annoying as an application where the developer has no clue about how term are used, but try to guess, or use some sort of dictionary lookup, missing a lot of the usage traditions.
For non-English UIs you have the additional problem that the developer / translator believes that the target language uses the same terms as in English, or a word very close. In some cases, this may be terribly wrong.
Have a professional from the application domain look over you UI with special attention to terminology. This applies even to English UIs.
|
|
|
|
|
The most basic UI design principle is this: Consider your audience.
Too many developers approach UI from the direction of "I have to support this set of operations on that set of data", and they design their UI accordingly. While that approach may satisfy requirements, it probably won't satisfy your users.
You need to put yourself in your user's viewpoint. Imagine yourself doing their job using your application. What should the application do to make that job easier? What operations do they always need? What operations are optional? Is there a required or natural order to those operations? What is the vocabulary employed by the user? In some cases you need to consider the user's level of education, training, and so on.
If you are localizing your application, you need to account for language translation issues. Text wrapping, hyphenation, and other layout concerns can be problematic.
One key notion is to meet your user's expectations - don't surprise them, and certainly don't frustrate them.
Software Zen: delete this;
|
|
|
|
|
We had it all figured out with windows, menu, toolbars, tooltips, right-clicks, color, etc.
Now for some reason it's more desirable to have black and white UIs with functionality that is barely discoverable, all in the name of accommodating touch screens.
IMNSHO, the "simplification" process apps are currently going through is not an "improvement".
|
|
|
|
|
[^]
that should do it. 
Arguing with a woman is like reading the Software License Agreement. In the end, you ignore everything and click "I agree".
Anonymous
|
|
|
|
|
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
One Norwegian webshop ("Arngren") is known by thousands of people due to their outright awful web design. I'd guess that half of the visitors to the site go there just to laugh at the look of it.
And it isn't new: In the old, pre-Internet days, Arngren was a classical mail order shop with product catalogs that were similarly awful; they just ported the same look to the Internet.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
