Mastodon is actively user-hostile, exhibit #24837: even in the discussion of a bug report, no one can give a straight answer about what "privately mention" means, and whether or not it is analogous to a Direct Message on other platforms.
I've watched many hundreds of #usability test participants type, and so make #typos.
Most commonly, the red wavy line (spelling error) causes people to backspace to the incorrect character, thus removing what they've typed, rather than using the arrow keys to reach the incorrect character, thus leaving the correct characters.
It's rare that people right-click a misspelled word to choose from a short list of suggested corrections.
While triaging some #Mutter issues in #GNOME, I saw a claim that the default "extend to external display on connect" behavior is confusing for some non-technical presenters.
Unable to trigger the issue using LibreOffice Impress, I did some #usability mind-reading and guessed that they must have been using a PDF instead of .odp/.pptx, in which case yes, the #UX would fail because the #Evince#PDF reader doesn't handle this correctly. Filed: https://gitlab.gnome.org/GNOME/evince/-/issues/1986
I absolutely, passionately, hate GUIs in which everything bounces around, spins, and whirs. Hold still already. Too much visual load. Everything screaming for attention at once, so I can't focus on anything.
Some games do this. Please stop. I've already decided to play. No need to jump around to get me to interact.
Hey, @Mastodon@Gargron, can you make it so the #ios client for mastodon shows us a little more of the poll option texts than, say, 15 characters? A word-wrap would be nice! #UX#usability#UserExperience
I’m honored to have been invited to a fireside chat with Steel City UX Ladies. They’re hosting the event, but it’s open to everyone. And it doesn’t cost anything other than an hour of your time.
Does anyone know of a good introduction to core usability considerations, aimed at non-developers? Things like discoverability, predictability, consistency, latency vs throughput, Fitts' law? Some colleagues who don't have a software background are getting in to digital health endeavours and I think it would be helpful for them to have some shared understanding.
If you're wondering why #java applications have a bad rep for #GUI#accessibility: the default GUI frameworks (SWT, JavaFX, Swing) are not accessible out of the box. None of the components support the keyboard shortcuts available on the various operating systems. It's like they were designed to be as different from everything else as possible. Thinking different hurts accessibility. Do better.
And it refuses to use the OS-native file open and save dialogs, replacing them with their own. Which offer none of the abilities users are used to using. And thanks. #usability#ux#userexperience
You may have found that #Microsoft refuses to call #usability in #MSWindows by its actual name. Instead, they insist on the trade-markable term "ease of access". And yet... the keyboad shortcut to open its settings is Windows-U. With U for...
More interesting #usability weirdness in #microsoft#windows: you can access the taskbar notification buttons using the Windows-B keyboard shortcut, then use arrow keys to activate the network listing... but can't use any keys to activate an available network. And thanks, @microsoft
Not sure how = and * got buried so deep in the iOS keyboard, either, but we have room for frequent symbols now on the surface of most devices, so wouldn’t that be great.
Bosch hat Schlüssel farbig kodiert.
An sich ja lobenswert.
Jetzt stell ich mal die Farbwahl in Frage .
Bei einem Tool das hauptsächlich von dem Geschlecht genutzt wird, das Pink nicht von Violett unterscheiden kann.
Ich hör schon die Diskussion...
"Eh Kalle, schmeiß ma den Ringschlüssel in Mauve rüber."
Kalle schmeißt.
"Man eh, det is doch nich Mauve Du Depp, det is Magenta. Der Mauve is da rechts der neben dem Flieder."
I'm a slightly autistic introvert, interested in a lot of things like surfing, design, technologies and computer science. Russian (native), English (foreign). 35+ yrs old.
The F-16A cockpit, designed in the early 1970s (in the era of slide rules), is still the epitome of an effective, efficient, ergonomic design. Its superiority is evident, when compared to the cockpits of its contemporaries, especially that of the F-15A. Another admirable UI design, albeit on a much smaller scale, is the Control Display Unit (CDU) of a typical Flight Management System (FMS). It, too, was designed in the 1970s. Such "industrial" UIs were designed, through iterative usability testing, by a team of psychologists, industrial engineers, electronic engineers, mechanical engineers, and experienced pilots.
In-cockpit, real-time UIs like these aims to decrease the potential for human error and to increase the pilots' situational awareness. They use the smallest possible set of usage conventions, control types, display components, fonts, and colours. They allow pilots to focus their attention completely on the critical information needed for the task at hand.
The traditional philosophy of human-machine interaction design is "usability without visibility". But today, the #web#UI's primary role is not #usability, but #marketability. And the users falsely equate flashy UIs with superior service.
This expensive trend is profitable to marketeers and attractive to casual users. So, it is justifiable for social media platforms and other non-mission-critical software. But this trend is unsuited to enterprise software, especially those designed for internal use. Such flashy antics diminish business users' #productivity and increases the company's #cost of ownership.
Designers should always test their work. And that goes for both digital and physical products.
I just moved into a new place with a pretty, designer sink that’s almost completely flat on the bottom, so the drainage is awful. Water just pools around, things like toothpaste or soap just sit there and don’t wash away into the drain. It’s very frustrating.
There’s no way the designer(s) could have used this sink without experiencing issues.
Since I have a gluttony for pain, I keep filing bugs in #LibreOffice regarding #UX#design problems. Two more filed this morning regarding the "Find and Replace" dialog (Ctrl+H). I know that dialog's #UI has a ton more #usability issues, but those particularly annoy me:
It's extremely disappointing that all the political parties I've investigated - including my preferred parties, #NZGreens, #TePātiMāori, and #TOP - all use US-owned proprietary software Nationbuilder. (I believe all the other political parties also use it) Politics in Aotearoa NZ needs to happen and be run here in NZ. What's the point if every single step of our political process here is framed and mediated by deeply untrustworthy US corporate interests? Kiss our sovereignty goodbye.
Identifying poor #HX (Human eXperience) in Free Code apps is not a condemnation of volunteer developers or their work. It's an explanation for people hesitating to use it.
An explanation that points to what can be done by those who want more people to make the switch. Especially in risk-averse and resource-constrained organisations like public service agencies, news media, and political parties.