Ideas for Future Research

1. Ideas for Future Research Anirudha JoshiIndustrial Design Centre, IIT Bombay February 2013

2. design for Indian needs human computer interaction software engineering

3. design for Indian needs human computer interaction software engineering • Text input in Indic scripts

5. Source: An Installation in IDC

8. Source: Anshuman Kumar

9. Without help p (one tailed) Nokia (0.208) Samsung (0.195) Sony (0.001) Total p (one tailed) Nokia (0.000) Samsung (0.010) Sony (0.000) Task Success /5 Users

10. Swarachakra • Logically structured (based on the structure of the script) • All consonants visible • Wheel with vowel modifiers pops up around the consonants

11. Swarachakra

12. Three Designs – Disha • Also completely logical • Consonants displayed in groups • Most frequent character in the centre, accessed on tap • Other characters need a slide • Finger input possible – large area for each button

13. Swarachakra

14. Evaluations • Independent variables • Age • Mobile phone experience • Education • Writing skills • Reading skills • Confidence of mobile phone task • First time usability test • 19 words graded on difficulty • Speed, errors, confidence • Longitudinal test • 10 short paragraphs typed over a period of 2 weeks in 10 sessions • Speed, errors, confidence

15. Results – Longitudinal Test: Speed

16. Results – Longitudinal Test: Errors

17. Results – Longitudinal Test: Confidence

18. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones

19. Evaluating Anonymous Social Networking for HIV Patients with Social Prototypes

20. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation

21. Way-finding Through Audio-Visual Interfaces • Can landmark-based navigation work for users with lower levels of education? • Two Audio-Visual Interfaces • Traditional map-based navigation with voice support • Landmark-based navigation with voice and picture support

22. Traditional Map-based Navigation

23. Landmark-based Navigation

24. Results India HCI 2012

25. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation • Usable security

26. Security Usable by Less Educated Users

27. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation • Usable security • Teaching Indic scripts to children

28. Toy for teaching Devanagari 1. Home-based Sitting-position Single/Multi player

29. CONCEPT 1 The child places the same alphabet again (चिड़िया).

30. CONCEPT 2 Lot of fishes come with the word मछ्ली.

31. Toy for teaching Devanagari

32. Toy for teaching Devanagari

33. Toy for teaching Devanagari

34. Toy for teaching Devanagari

35. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation • Usable security • Teaching Indic scripts to children • Localisation

37. Principles of Good Localisation • Simplify, un-sanskritise text • कळफलकसक्रीयकुलुपकाढले, विकल्पपर्याय • Use explicit noun-verbs • Call (make call) = कॉलफोनकरा • Cool commands, metaphors are lost in translations • Go (where?) = जाशॉर्टकट • Answer = उत्तरफोनघ्या • Register = नोंदआल्यागेल्याफोनच्यानोंदी • Don’t use English words where you don’t need them • अनलॉककुलुपकाढा • Use English words where you need them • Loudspeaker = ध्व.क्षे. स्पीकर • Contacts = संपर्कडायरी, Edit number = संपर्कसंपादननंबरबदला • Get the grammar right (sequence matters) • “कॉलहोतआहेनिखिल” “निखिललाफोनहोतआहे”

38. Localisation

39. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation • Usable security • Teaching Indic scripts to children • Localisation • HCI+SE process integration • Goals for specific contexts • Industrial, commercial, social • Software ethnography

40. Contributions 1/3 importantgoals are not achieved 8 “latent” goals Relative contribution of HCI activitiesto usability goalsachievement HCI Activities Framework Usability Goals Setting Tool informs integration with activities that contribute to Project follows results in Waterfall helps set Agile Process Product is compared to has RUP Goals Process models integrating HCI activities with SE evaluates fidelity evaluates the design against Index of Integration Usability Goals Achievement Metric Correlation Validated by comparing with traditional UEs Agile vs.Waterfall Product vs.Services validates

41. design for Indian needs human computer interaction software engineering • Text input in Indic scripts • Design for people with less education • Appropriate user models for emerging economies • Audio-visual interfaces • Voice-based socialisation on phones • Way-finding and navigation • Usable security • Teaching Indic scripts to children • Localisation • HCI+SE process integration • Goals for specific contexts • Industrial, commercial, social • Software ethnography