1. #+ professor patrick baudisch hci1: designing interactive systems hasso-plattner institute discrete, text, menus

2. for discrete tasks use discrete controls & techniques (such as buttons for typing or launching app) use pointing controls for pointing tasks

3. most of you will want 1. one or more types of discrete input (“buttons”) 2. one or more types of continuous input (“pointing”)

4. discrete input

5. keypad d-pad/ joystick qwerty keyboard

6. [PARC Tab] three buttons on the PARC tab

7.  Scott MacKenzie

8. text entry using gestures

9. hand writing reco

10. anoto

11. unistroke [Goldberg] reliable tokenization

12. graffiti more guessable

13. graffiti 2 Why did they change this?

14. June 28, 2006 Unistroke Payoff “Palm has agreed to pay Xerox $22.5 million to settle its long-running unistroke patent infringement suit.”

15. edgewrite [wobbrock] edgewrite works on joysticks, pen, touch, device backside..., is guessable

16. dasher slow, not intuitive as it may seem (try it out)

17. quikwriting benefit: concatenate strokes... h=

18. shark = shapewriter concatenate and leave out strokes...

19. let’s reflect…

20. buttons (e.g., keyboards) vs. gestures? pros and cons, when to use what?

21. tradeoff: buttons require minimum space, visual control gestures can be performed eyes free, but are all but impossible to discover

22. discoverability is a huge thing. for many applications a show stopper

23. that said: reminder… discoverable: users figure it out (without a tutorial?) efficient: allows performing tasks quickly robust: minimal error rates; help users recover pleasing/fun: high user satisfaction usability does not mean you always have to design for novices (but know who you design for)

24. two main usability goals for this tabletop: (1) discoverability (2) fun/pleasing probably no gesture here

25. most of these are simply gesture training devices

26. marking menus [Kurtenbach & Buxton, '91] alias sketchbook one that particularly well for 8 of fewer choices

27. linear menus require visual control marking menus can be used eyes-free

28. how to handle more than 8 choices?

29. 29 compound marks

30. limitation: need space NE-E -NE-E

31. simple marks

38. limitation of simple marks?

39. how to abort half way in? forget that I have a mark already  error (they are “modal”)

40. there is no free lunch

41. minority

42. gwindows

43. [Rekimoto, GestureWrist, ISWC 2001] gesturesWrist uses accelerometers

44. [Wilson, Flowmouse] gestures observed by camera

45. [gesture pendant, starner et al ISWC 2000] wearable camera

46. motion capture system = set of cameras and markers (gold standard, used by film industry)

47. data glove measures position of hand and angle at finger joins

48. the term gesture is overloaded: motion vs. posture of the hand

49. gestures on tiny hardware

50. “scanners” := devices that users operate by moving their hand across [disappearing mobile devices, Ni & Baudisch, 2009]

51. 1. motion scanner camera (as in mouse) seen as “curve right, curve right” recognized language is unistroke-like

52. graffiti “a” virtual scroll ring but: motion sensor = camera  requires certain size

53. 2. touch scanner touch sensor seen as “..” recognized language ismorse ~pressing a button [Fukomoto]

54. one finger = 1 two fingers = 2

55. 3. direction scanner 3 touch sensors seen as “east east” recognized language issimple marks

56. “west” “south”

57. touch scanner direction scanner motion scanner entering a “2” “NE” “..” “2”

58. # errors (out of 96) 5 letters = two thirds of errors error edgewrite works well (~5% error) most of graffiti works

59. edgewrite is entirely based on recognition of corners users can perform these eyes-free graffiti uses an additional type of feature: whether and where two strokes intersect graffiti error

60. large gestures (on non-mobile)

61. menuing

62. also discrete, not really different from text entry

63. keypad d-pad/ joystick qwerty keyboard can use same devices…

64. thumb wheel offers detents eyes-free

65. no detents 