|
|
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.
|
|
|
|
|
Excellent topic.
This is the kind of stuff that makes the internet worth having in the home.
|
|
|
|
|
|
thank you thank you thank you thank you thank you
|
|
|
|
|
Every single mediocre in a big company creates "guide" how he sees the UI. Lots of 'em. But UI is a very specific to application, so you cannot give "universal advice - every case should be considered.
|
|
|
|
|
Agreed. But that doesn't mean that every application is free to do it whichever way the developer chooses: In many professional areas, there are established ways for how to do things across a number of competing alternatives. Sort of like a "GUI professional terminology" - if you want to change that terminology you should be fully aware of that and do it with a clear intent.
My honest opinion is that one major reason why *nix failed on the desktop was that developers more or less completely ignored conventions and terminology, and made things the way the programmer thought would be some great idea, without ever asking professionals for their opinion (or if he did, ignoring their answers). Advanced users didn't feel at home; the application didn't "think" the way they did as professionals.
So, take the freedom to listen to domain experts. Don't take the freedom not listening to domain experts.
|
|
|
|
|
I-net is full of such "UI guides", I don't know what a problem topic starter has.  But looking at his questions (where to place controls) he is not even googled it.
|
|
|
|
|
Maybe he was asking for wisdom. Not just google matches.
If you do not distinguish between wisdom and google hits, then you are like that capitalist who knows the price of everything and the value of nothing.
When I ask for advice from a person, I am asking for that person's experience, knowledge, judgements and wisdom. Not for his google hits.
|
|
|
|
|
Wisdom?? LOL! So he is so lazy not even googling proper articles, but expects somebody will waste time on creating article? It's at least naive, at most it's stupid. It's too wide topic to ask in this place.
|
|
|
|
|
To me, the epitome of lazyness is "helping" someone by telling them "Just google it!"
|
|
|
|
|
Just like building a building... Form follows function.
Lets say a user has to enter 12 pieces of data. That data comes to them from 3 sources.
I would think that grouping the inputs according to source MIGHT make sense.
I do not believe there is a one size fits all answer. Look at PowerPoint, Excel, and Word. Similar GUI interfaces, and radically different GUI Interfaces at the same time. Put a formula in a table in word. you can do it. Much hard than a formula in a cell in Excel.
Here are some things to consider:
1) What the users want
2) Who the users are
3) Why does the software exist (Hint: to make someones life easier/better=>It's about people)
4) Is it clear what is expected
5) More people are Color Blind than you realize (like myself)
6) How often is it used? (a nice click sound is great on confirmation. But not on confirmation of something that I have to do 1,000 times a day, every day. Imagine a Whoot Whoot sound played on a McDonalds screen after every order is entered. Then imagine a busy lunch with 4 registers going at once)
7) Use it yourself, LIKE your user would
8) use it half way, walk away, come back (like you got interrupted), and figure out how to complete it.
Finally, it is as much art as science. And it also depends on the Platform, and the device.
Many things work fine on a PC screen, suck on a mobile screen, impossible on a DOS screen, horrible on a paper terminal (for those of us who have been through all of them).
|
|
|
|
|
I haven't read all of the replies, so please forgive me if I'm repeating others.
My one overarching general principle is, "maintain the context".
There is nothing worse than being in the middle of a process and forgetting why you're there and what choices you've made.
So, for left-to-right I keep the highlighted context queues on the left and the detail on the right.
For right-to-left, the context is on the right.
For top-to-bottom, the context is on the top.
That kind of eye-flow, that parallels the natural way people read, helps keep the experience intuitive and minimizes user stress.
Oh yeah! In my experience it doesn't happen very often these days, but use contrasting colors for text and background. There is nothing more aggravating than being unable read text that blends into the background like yellow on line green for example.
Good luck to you!
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
|
|
|
|
|
|
See About Face - The Essentials of User Interface Design by Alan Cooper
https://www.amazon.com/About-Face-Essentials-Interface-Design/dp/1568843224
See also Balsamiq - a reasonably decent UI prototyping app at www.balsamiq.com
|
|
|
|
|
Years ago both Microsoft and IBM developed concepts for intuitive interfaces. However, it was Apple Corporation that made interface design into an art form.
With the exception of Apple, developers in the Microsoft and IBM communities appeared to go their own ways as to how to best design an intuitive interface.
I do not know about the IBM side of things but when everyone was demanding standards back in the 1990s Microsoft did attempt to satisfy this demand by promoting a number of standards for development of applications, including design concepts for the interface of graphical applications. Then suddenly the Microsoft Development Community turned on Microsoft making the claim that the company was now trying to dominate the industry.
In any event, user interface design concepts were made available in a variety of ways.
The links below will give you an idea as to what standards were being promoted and most likely are still quite relevant to today's development efforts... (an article on Apple design is the 3rd link)
https://msdn.microsoft.com/en-us/library/ms997506.aspx
http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html
https://developer.apple.com/design/tips/
To research this design area further enter the following search terms into your preferred search engine... common user interface design
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
