The document provides interaction design tips and best practices, listing "do's and don'ts" for interaction design. It recommends that designs be beautiful, fast, expressive, accessible, and work across devices. Specific tips include making designs that follow key principles, keeping the end user in mind rather than personal preferences, using states metaphors rather than frames, and differentiating necessary features from nice-to-haves. The document cautions against assuming users will adapt to poor designs or prioritizing workflows over interaction design.

1. Interaction design do’s & don’tsharish sivaramakrishnancomputer scientist & evangelistAdobe Systems

2. experience matters!

3. Interaction designThe 5 demandments.

4. beautiful

5. fast & agile

6. expressive

7. accessible

8. everywhere!

9. Flexibility is key.

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 PagesRIA’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 aretechnology agnostic.

16. exhibit A forbad design and programming aretechnology agnostic.http://bouncebargainrentals.com/

17. exhibit B forbad design and programming aretechnology agnostic.http://www.html5zombo.com/

18. DO:Make a design that concurs to the demandmentsDON’TRehash your existing design with a new technology.

19. DO:Keep in mind the multiple form factors your app needs to work on.DON’TBuild hard wired layouts, whenever you can.

20. DO:Small devices need larger clickable areas. Design your controls for that.DON’THard port your Web UI to small devices, it’s a different screen, different metaphor.

21. DO:Give haptic feedback, wherever necessaryDON’TDo random things in the name of haptic feedback

22. DO:Use your creative freedom keeping your end user in mind. DON’TInvent knee-jerk patterns.

23. DO:Maintain the identity of a control while creating experiences around it. DON’TMake buttons look like rockets and scroll bars look like UFOs.

24. DO:More in one place. Use the states metaphor. DON’TMake 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.comtwitter: @hsivaramweb: http://blog.flexgeek.in