Thursday, October 2, 2014

Do it yourself usability design for developers

Usability
Learnabilty- how long to learn first simple task
Efficiency - how long for experienced user with difficult task
Memorability- how long for experienced user who's been away and is coming back to complete difficult task
Errors - how many errors and recovery time,
Satisfaction - feel good factor

The curse of knowledge is what to tell users to train them. Not too much nor too little.
Can't really see ui from user perspective. They get stuck.



Process and tools
Look at other crafts. Painting create sketches, study posture. We should take same approach.
Two curves: complexity (start low) and parallelism (start with many designs and eliminate)
Don't g et attached to design, easier to take feedback if have several versions in parallel.
Sketches important. As many as you can think of of. 5,6 8. 5 mins, 6-8 sketches. Get into flow.
Paper prototype. Create all the screens. One person plays user, another the computer swapping screens.
Lofi prototype. Wireframe designs. Or powerpoint, make interactive, only good for simple though. Can be used by many.
Simplified app with very little logic is an alternative.
Lofi can leave you frustrated.
Hifi prototype. Usability questions should be answered. Not all functionality.



Ux techniques
Field study. Watch users doing tasks. Check out competition or manual workarounds.
Persona. A description of a user group, a typical representative. Used to answer questions. Have empathy for character. Difficult to create.
Proto-persona. Ad-hoc persona that you keep improving. A guess.
Empathy map. (diagram)
Heuristic evaluation. Colleagues from another team or project. These experts do tasks and they report on heuristic. Visibility, match between system and real world (same terms?),user control and freedom - recover from errors. Report on most important heuristic. Can provide false positives. Low cost.
Usability test - mics and cameras. Usually out of reach because of cost. Alternative is screen recording or screen sharing. Participant should have never seen app before. Craig's list. Important to stress app is being tested not participant. Stuck good. No help during test. Ask to think out loud. Whole team should evaluate. 3-5 participants is enough, fix, another round.


1 comment:

  1. This is an excellent post for developers, I prefer to every fresh developer to read this post and will our activities according to this post. event applications android

    ReplyDelete