4 ms·

Apps ought to be designed with these UI guidelines in mind: Here's what I'm working on right now, and how long it may take. Status feedback fosters trust. I s

Apps ought to be designed with these UI guidelines in mind: Here's what I'm working on right now, and how long it may take. Status feedback fosters trust. I speak your language. Jargon is confusing. You can take things back. Undo grants freedom from frustration. I behave just like the others. Inconsistent conventions increase cognitive load. Are you sure? Confirm before commit. Eliminate slips & mistakes. A slip is an unconscious, inattentive error. A mistake is a conscious error, but domain (mental model) mismatch. I auto-populated these fields. Design so interface favors recognition over recall. Ways to make you more efficient. Enable power-users. Aesthetic & minimalist, but not necessarily flat design. I've written stuff so you can learn more about me. Provide help and documentation. --- As I worked on this, I realized some of this could improve communication between people.

prox 4y ago
Pliancy : this is something you can manipulate
- turtleyacht 4y ago
  Thank-you. Porcelain vs plumbing
kitsunesoba 4y ago
> You can take things back. Undo grants freedom from frustration. > Are you sure? Confirm before commit. Eliminate slips & mistakes. A slip is an unconscious, inattentive error. A mistake is a conscious error, but domain (mental model) mismatch. Additionally, don't use the former as a replacement for the latter. While a way to undo destructive things should be present wherever possible, they should also be prevented from happening in the first place where reasonably possible. Google apps are bad about this. Rather than add a small amount of friction to avert common types of disasters, they tend to lean on undo, which works fine until you end up too distracted to notice the little "X happened [Undo]" notification until you realize what happened a week later when the action you accidentally committed has become irrevocable.
- graypegg 4y ago
  An example of a product that has a well made undo feature is Jetbrains’ IDEA. Whole file operations (move, delete, rename) and refactoring tasks are included in the undo stack. They even let you browse the undo stack in the “local history” tool, which has totally ruined a lot of other editors for me.
prime17569 4y ago
Apple's old OS X Human Interface Guidelines (pre-OS X Yosemite)[1] said almost exactly the same things. https://web.archive.org/web/20140603021344if_/https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/AppleHIGuidelines/OSXHIGuidelines.pdf https://web.archive.org/web/20140603021344if_/https://develo...
graypegg 4y ago
I kept your receipts: don’t create leaves in your navigation tree that can be only accessed once. An example is “order complete” screens that aren’t under the “active orders” or “receipts” page, but are their own special page that the user isn’t sure if they can get back to.

prox 4y ago

Pliancy : this is something you can manipulate

turtleyacht 4y ago
Thank-you. Porcelain vs plumbing

kitsunesoba 4y ago

> You can take things back. Undo grants freedom from frustration. > Are you sure? Confirm before commit. Eliminate slips & mistakes. A slip is an unconscious, inattentive error. A mistake is a conscious error, but domain (mental model) mismatch. Additionally, don't use the former as a replacement for the latter. While a way to undo destructive things should be present wherever possible, they should also be prevented from happening in the first place where reasonably possible. Google apps are bad about this. Rather than add a small amount of friction to avert common types of disasters, they tend to lean on undo, which works fine until you end up too distracted to notice the little "X happened [Undo]" notification until you realize what happened a week later when the action you accidentally committed has become irrevocable.

graypegg 4y ago
An example of a product that has a well made undo feature is Jetbrains’ IDEA. Whole file operations (move, delete, rename) and refactoring tasks are included in the undo stack. They even let you browse the undo stack in the “local history” tool, which has totally ruined a lot of other editors for me.

prime17569 4y ago

Apple's old OS X Human Interface Guidelines (pre-OS X Yosemite)[1] said almost exactly the same things. https://web.archive.org/web/20140603021344if_/https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/AppleHIGuidelines/OSXHIGuidelines.pdf https://web.archive.org/web/20140603021344if_/https://develo...

graypegg 4y ago

I kept your receipts: don’t create leaves in your navigation tree that can be only accessed once. An example is “order complete” screens that aren’t under the “active orders” or “receipts” page, but are their own special page that the user isn’t sure if they can get back to.