Intuitive Interfaces
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
people who design and write interfaces should have the interfaces tested by novices in their presence, from day one. The designer is a bit subjective without this feedback. Ideally the designs should be driven by objective user test results. Boeing learned this when designing interfaces for their users. They found that subjective test data from experts (pilots, etc.) was not as good. Pilots all had various opinions about interfaces so Boeing went to objective testing results to find the most efficient design. Side note: I once flew in a Boeing simulator with zero flying experience. With the destination already set, I took off, flew and landed with minimal instructions. Very cool, except I blew out the tires landing too fast and steering too sharp. Their simulator even had that part of the landing modeled. That's the objective test results they were getting.
"A little time, a little trouble, your better day" Badfinger
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
People who design and write interfaces should have the interfaces tested by novices in their presence, from day one. The designer is a bit subjective without this feedback. Ideally the designs should be driven by objective user test results. Boeing learned this when designing interfaces for their users. They found that subjective test data from experts (pilots, etc.) was not as good. Pilots all had various opinions about interfaces so Boeing went to objective testing results to find the most efficient design. Side note: I once flew in a Boeing simulator with zero flying experience. With the destination already set, I took off, flew and landed with minimal instructions. Very cool, except I blew out the tires landing too fast and steering too sharp. Their simulator even had that part of the landing modeled. That's the objective test results they were getting.
"A little time, a little trouble, your better day" Badfinger
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Is that page supposed to lead somewhere? I tried clicking the big NO button and the words "click here" but nothing.
The difficult we do right away... ...the impossible takes slightly longer.
-
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Is that page supposed to lead somewhere? I tried clicking the big NO button and the words "click here" but nothing.
The difficult we do right away... ...the impossible takes slightly longer.
Which only means that the UI made to perfection :laugh: (try HERE, but at your own risk - it is even worst after that)
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
Buy them a helicopter. That stll has been the record holder for the most intuitive user interface since it was invented. Brave men, these flight instructors.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
Is that page supposed to lead somewhere? I tried clicking the big NO button and the words "click here" but nothing.
The difficult we do right away... ...the impossible takes slightly longer.
It says "Please click HERE ..." so you obviously have to click HERE... :rolleyes: And that one was easy compared to what's coming :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
7 minutes... That is terrible. Sander, you are a bad person. :laugh: :laugh: :laugh: :laugh: :laugh:
www.robotecnik.com[^] - robots, CNC and PLC programming
4:21 and I actually selected MY OWN COUNTRY FLAG! :D That flag is absolutely terrible, took me over a minute (selected Luxembourg first) :laugh:
User Inyerface wrote:
YOU ARE AWESOME! A true interface legend. [Dancing Carlton from The Fresh Prince of Bel-Air gif]
Joan M wrote:
Sander, you are a bad person.
Yeah, I get that a lot :D
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
That is truly obnoxious. It took me 11:49 to get to the dancing Carlton. I'd hazard a guess that the author of that horror copied about 80% of the instances of idiocy found on that interface from sites they had encountered at one time or another. I know that I've run across several of them. My pet Peeve is password requirements that don't specify a maximum length. I also hate "you must use a special character" ... Oh, sorry, "&" is invalid.
-
I am sitting here trying to do some work while alongside me my wife is attempting to set up a Zoom discussion with a friend. Neither of them know what they are doing, so it has been interesting hearing their learning curve. At least it was at the start, now I will have to go and chop some firewood before my blood pressure goes off the scale. I know that I find that interface fairly transparent, but maybe they need a "just heard about computers" interface as an option?
"The wife with a friend". Zoom isn't the priority.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
people who design and write interfaces should have the interfaces tested by novices in their presence, from day one. The designer is a bit subjective without this feedback. Ideally the designs should be driven by objective user test results. Boeing learned this when designing interfaces for their users. They found that subjective test data from experts (pilots, etc.) was not as good. Pilots all had various opinions about interfaces so Boeing went to objective testing results to find the most efficient design. Side note: I once flew in a Boeing simulator with zero flying experience. With the destination already set, I took off, flew and landed with minimal instructions. Very cool, except I blew out the tires landing too fast and steering too sharp. Their simulator even had that part of the landing modeled. That's the objective test results they were getting.
"A little time, a little trouble, your better day" Badfinger
That’s a fantastic post & a great example. UI Designers often blame the user or say “well it’s complex software so the UI is complicated.” But your example shows that even something as complex as piloting a jet aircraft could be simplified for general use if the designers cared to do so. Have you read The Design of Everyday Things: Revised and Expanded Edition - Kindle edition by Norman, Donald A.[^] The book explains how designers often do things wrong then blame the user and the users often feel stupid even though they really aren’t. The design just makes them feel that way.
-
That’s a fantastic post & a great example. UI Designers often blame the user or say “well it’s complex software so the UI is complicated.” But your example shows that even something as complex as piloting a jet aircraft could be simplified for general use if the designers cared to do so. Have you read The Design of Everyday Things: Revised and Expanded Edition - Kindle edition by Norman, Donald A.[^] The book explains how designers often do things wrong then blame the user and the users often feel stupid even though they really aren’t. The design just makes them feel that way.
You overlook the stupidity of management. Before I retired, I tried to design based on real user input. Often, when I demo'ed the result to management, they just had to change it, making it needlessly complex and cumbersome to use. Instead of putting the most common two or three items at the top of a list followed by the remainder of the choices in alphabetic order, they required full alphabetical order.
For example, let us look at selecting client language. In the United States, English and Spanish are the most common languages; they would require Africaans and Arabic at the top of the list and Spanish way down below Farsi, German, Korean, Portuguese, Russian and a host of others.
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
-
You overlook the stupidity of management. Before I retired, I tried to design based on real user input. Often, when I demo'ed the result to management, they just had to change it, making it needlessly complex and cumbersome to use. Instead of putting the most common two or three items at the top of a list followed by the remainder of the choices in alphabetic order, they required full alphabetical order.
For example, let us look at selecting client language. In the United States, English and Spanish are the most common languages; they would require Africaans and Arabic at the top of the list and Spanish way down below Farsi, German, Korean, Portuguese, Russian and a host of others.
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
I wouldn't call this management "stupidity". It's trying to make it look as if you add value even though you're far from expert in, or have only put superficial thought into, what you're commenting on. Code reviews are just as useless when "reviewers" harp on variable names or formatting because they have nothing to say about design or merely skimmed the code and missed bugs that could have been spotted with due effort. I would have told them that the UI was carefully considered, that their input would be noted but that they would not be making decisions on the UI, and that the demo's purpose was to show that a milestone had been reached and provide a preview of what would be shipping.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
That’s a fantastic post & a great example. UI Designers often blame the user or say “well it’s complex software so the UI is complicated.” But your example shows that even something as complex as piloting a jet aircraft could be simplified for general use if the designers cared to do so. Have you read The Design of Everyday Things: Revised and Expanded Edition - Kindle edition by Norman, Donald A.[^] The book explains how designers often do things wrong then blame the user and the users often feel stupid even though they really aren’t. The design just makes them feel that way.
Thanx. I haven't read the book you referenced, but its now on my Amazon buy list. My experience occurred in 1994 when the 777 made its first flight. The company I was working with flew a group of us to Boeing in Seattle for a mini-conference to discuss designing user interfaces. The 777 was the first aircraft (they say) that was designed, built and tested using electronic design and simulation software. Boeing, of course, does not always follow their advice (737[^] User interfaces are first driven by requirements, which management usually has complete control (their mistake if not include the interface designers). Requirement creep is usual the reason for management intervention and not always well done. Oh well, not a perfect world.
"A little time, a little trouble, your better day" Badfinger
-
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Funny stuff. BTW one of UI topics some of my team researched with objective testing was the YES/NO, ON/OFF, etc (binary states). User confusion of what is the current state versus changing the state is increased. One button, versions and two buttons versions. The human subject testing was quite thorough and comprehensive. There were multiple phases of this testing. In aerospace a mistaken judgement of the system state could be fatal. BTW Apple users a sliding binary button which is quite effective. Their UI is generally pretty good but not always obvious.
"A little time, a little trouble, your better day" Badfinger
-
You overlook the stupidity of management. Before I retired, I tried to design based on real user input. Often, when I demo'ed the result to management, they just had to change it, making it needlessly complex and cumbersome to use. Instead of putting the most common two or three items at the top of a list followed by the remainder of the choices in alphabetic order, they required full alphabetical order.
For example, let us look at selecting client language. In the United States, English and Spanish are the most common languages; they would require Africaans and Arabic at the top of the list and Spanish way down below Farsi, German, Korean, Portuguese, Russian and a host of others.
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
-
You overlook the stupidity of management. Before I retired, I tried to design based on real user input. Often, when I demo'ed the result to management, they just had to change it, making it needlessly complex and cumbersome to use. Instead of putting the most common two or three items at the top of a list followed by the remainder of the choices in alphabetic order, they required full alphabetical order.
For example, let us look at selecting client language. In the United States, English and Spanish are the most common languages; they would require Africaans and Arabic at the top of the list and Spanish way down below Farsi, German, Korean, Portuguese, Russian and a host of others.
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
Isn't that an excellent example of a developer centered design? If you sit e.g. in Norway, as I do, or in some East European, Asian or African country, English or Spanish is not the primary language alternatives! You may say "But the US is our primary market! (Besides, that is where I am living ...)", fair enough if you simply do not care about other markets. Why then worry about all these other languages at all, if you do not care about the users of those languages? In Windows - but also in *nix - the environment always informs you about the locale and the preferred language. If you really cared for the user, you would honor that. If you want to do the job well, you would use the locale to select not only the top entry, but a few more down the list, such as French and English as the two top entries in Canada (if the user's preferred language is a third one, it obviously goes ahead of both). If the user at some time has selected yet another alternative, he is probably making use use of that language, so put any explicitly selected language up on top as well. Then you can list the rest of the languages - those with no indication of being relevant to the user - in alphabetical order. Those that goes on top are those that are more likely to be chosen by the user. And not those preferred by the developer! This obviously goes for all locale related UI aspects, not just the language, but e.g. date and numeric formats and lots of other things. If you use system provided functions for the formatting, you may evade the issue, until the user is given a chance to select some other format, some other value. Say, a valuta calculator: A user in Norway who sees USD on top of the list every time, even after having selected NOK a hundred times before, gradually gets sort of p***ed. If you don't care to do a proper job, then you might as well do as your boss says: Do not give any preference to any choice. Giving preference to your choice, rather than that of the user, does not improve the quality of the user interface.
-
This one always gets me: User Inyerface - A worst-practice UI experiment[^] :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
