Interaction design Do's & Dont's
•
7 likes•1,579 views
Presented at Adobe Flash Platform Summit 2010, Bangalore, India
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Interaction design Do's & Dont's
Similar to Interaction design Do's & Dont's (20)
Recently uploaded
Recently uploaded (20)
Interaction design Do's & Dont's
- 1. Interaction design do’s & don’ts harish sivaramakrishnan computer scientist & evangelist Adobe Systems
- 3. Interaction design The 5 demandments.
- 4. beautiful
- 5. fast & agile
- 6. expressive
- 7. accessible
- 8. everywhere!
- 10. RIA !=Jazzy (?)
- 11. Don’t take users for granted. Incorrect: I know my users, they will eventually come to terms with my UI / UX
- 12. Workflow is not the only King! Incorrect: Interaction design *only* if I have time.
- 13. HTML has Pages RIA’s Don’t! Hence, If your interaction design means page migration. Press the panic button. Now!
- 14. Animations are nice. Only when relevant. Don’t re-invent skip intros
- 15. bad design and programming are technology agnostic.
- 16. exhibit A for bad design and programming are technology agnostic. http://bouncebargainrentals.com/
- 17. exhibit B for bad design and programming are technology agnostic. http://www.html5zombo.com/
- 18. DO: Make a design that concurs to the demandments DON’T Rehash your existing design with a new technology.
- 19. DO: Keep in mind the multiple form factors your app needs to work on. DON’T Build hard wired layouts, whenever you can.
- 20. DO: Small devices need larger clickable areas. Design your controls for that. DON’T Hard port your Web UI to small devices, it’s a different screen, different metaphor.
- 21. DO: Give haptic feedback, wherever necessary DON’T Do random things in the name of haptic feedback
- 22. DO: Use your creative freedom keeping your end user in mind. DON’T Invent knee-jerk patterns.
- 23. DO: Maintain the identity of a control while creating experiences around it. DON’T Make buttons look like rockets and scroll bars look like UFOs.
- 24. DO: More in one place. Use the states metaphor. DON’T Make an app that looks like a <frameset>, that’s oh! So 90s!
- 25. let’s fix our part first. before we blame the technology.
- 26. let’s differentiate between “can” and “should”.
- 27. let’s differentiate between “want” and “need”.
- 28. While making technology choices, let’s not take sides. remember, their battle is not our battle.
- 29. questions?
- 30. email: hsivaram@adobe.com twitter: @hsivaramweb: http://blog.flexgeek.in