uracreative
/
ura.design
mirror of https://github.com/uracreative/ura.design
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

Update 2018-07-02-style-guides-go-beyond-aesthetics.md

redesign
Elio Qoshi 7 years ago
committed by GitHub
parent
6b27a6e3f7
commit
9545fa8594
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      _posts/2018-07-02-style-guides-go-beyond-aesthetics.md

2
_posts/2018-07-02-style-guides-go-beyond-aesthetics.md
View File

@ -20,7 +20,7 @@ Oftentimes we witness the results of elitist practices upon users, usually worde
A similar stigma often appears in Free Software / Open Source projects as well. The alternative "*Read the Documentation*" certainly would ensure that people would give a little more effort before repeating questions. With limited resources it's also understandable that this might be the most sane way for a project maintainer to channel user interactions. However is that by design or due to lack of resources? One could argue that it would make more sense to integrate those 'user lessons' right inside the application instead of a manual or documentation alone. A similar stigma often appears in Free Software / Open Source projects as well. The alternative "*Read the Documentation*" certainly would ensure that people would give a little more effort before repeating questions. With limited resources it's also understandable that this might be the most sane way for a project maintainer to channel user interactions. However is that by design or due to lack of resources? One could argue that it would make more sense to integrate those 'user lessons' right inside the application instead of a manual or documentation alone.
## Manuals are the Minimum Viable Product of a Product's Usability. ## Manuals are no replacement for good Usability
Make a great manual and a mediocre application and you might be able to keep a user from running into blockers, however you won't be able to improve their workflow. The user is basically learning an app by heart, not by intuition. Make a great manual and a mediocre application and you might be able to keep a user from running into blockers, however you won't be able to improve their workflow. The user is basically learning an app by heart, not by intuition.

Write Preview
Loading…
Cancel
Save