Earlier quoted context omitted.
That's the "chrstphrknwtn principal", use whichever principal best applies.
This is the "jonny_eh meta-principle" at work! Finally see it with my own eyes!
I, personally, see it everywhere!
Laws of UX
111–114 of 114 posts
Re: Laws of UX
#112My ideal for UX or UI is that a new user, understanding the domain and what the application is supposed to do at the most abstract level, should be able to immediately use it without any training or explanation.
Discoverability is an underrated feature in software. I like how in Microsoft Word (off the top of my head), all shortcuts are displayed when you go to the file menu.
Redundancy is also an underrated design feature. In Word, if you want to copy/paste, there are at least 3 ways (I'm sure I'm missing some obscure way).
- menu->edit->copy
- right click->context menu->copy
- ctrl-c
And it's a great way of transitioning users from new mode to expert mode. A hotkey is just about useless if you don't know it exists, whereas the menu is slow. So, beginner users start using the menu, then transition as they memorize the particular hotkeys for this software as they become expert users. Somebody put thought into this design.
Also taking this opportunity to shamelessly plug the nested tooltips in Crusader Kings III. As far as learning context in-situ without breaking flow, it is amazing, though sadly not generalizable to all applications. Seriously, whoever designed that needs another raise; I have yet to see a minor UI component receive any mention at all, let alone praise, save this one.
https://www.reddit.com/r/CrusaderKings/comments/102gtm8/nest...
Re: Laws of UX
#113These seem like theories, not laws. And imho, some of it is very wrong, such as: > Purposefully adding a delay to a process can actually increase its perceived value and instill a sense of trust, even when the process itself actually takes much less time.
I added a 2 second delay to a near instant process and made it feel significantly better and like “something happened”. When it was instant it felt … wrong.
If I were you're user, I'd appreciate a setting to remove all such delays. That is, assuming I've little chance of convincing you to remove them permanently. (-:
Re: Laws of UX
#114Earlier quoted context omitted.
I experienced this first hand with the manual sync button on one of my apps. I got feedback stating it didn't work when, in reality, there was no work to be done and the interface didn't have time to display 'syncing' before it finished. The solution was to add a 50-300ms delay before the network request. Why? Because feelings and perception matter more than facts.
I see a lot of comments here about added animations because the request is too fast. In this case I would guess the issue is not with speed but feedback. The user did something, nothing changed, so they thought it was broken. Instead of the delay you could add a toast or some text with near the button indicating that the action actually happened.
Moderate preference for the added text, rather than an an ephemeral 'toast' message.