Published on

  • Be the first to comment

  • Be the first to like this


  1. 1. Interaction Design<br />A1 Presentation<br />Culture Cow<br />
  2. 2. Key Functional Requirements<br />Encourage user interaction through tamagotchi character.<br />Allow users to upload and find videos, recipes, stories and pictures for sharing.<br />Control tamagotchi’s happiness through uploading or downloading.<br />Users can request content from users sharing mutual nationality, age or religion.<br />Support potential user growth with register / login feature <br />
  3. 3. Key Non-Functional Requirements<br />User<br />Fun, inquisitive experience to form trust and a bond with the user.<br />Provide refreshing and exciting interface that addresses user engagement issues in University domain.<br />Usability<br />Provide accessible menus to users of all languages.<br />Data<br />User data - email and password - will be recorded on a secure database.<br />Environment<br />Provide an interface that can be used in both a quiet or busy environment. <br />
  4. 4. Scenario - Carlos<br />Description:<br />Culture cow sign up<br />Objective:<br />Carlos needs to sign up for the culture cow application and configured the tamagotchi.<br />Background:<br />Carlos is a 28 year old student who has just moved to Bristol.<br />Carlos is Spanish and this is his first time in England. <br />He wishes to study and get a good grade and is worried it might be hard to keep in contact with his family. <br />He has trouble making friends.<br />
  5. 5. Scenario storyboard<br />
  6. 6. Interaction Flow<br />Overview of interaction within the application.<br />Shows possible user paths<br />The way user actions affect the tamagotchi’s happiness<br />
  7. 7. Lo-Fidelity Prototypes<br />
  8. 8. Reflective Review of Prototypes<br />
  9. 9. Reflective Review of Prototypes<br />Early paper prototype<br />Lack of affordance for entering name and location details<br />Moved from underlines to boxes<br />Not refined for keyboard<br />Changed form size to allow for keyboard to slide up<br />
  10. 10. Reflective Review of Prototypes<br />Early paper prototype<br />Overly technical jargon, media type was inappropriate for audience.<br />Simplified to icons rather than drop down box.<br />Options button changed to icon, a cog. <br />Movement away from language to universal symbols.<br />
  11. 11. Reflective Review of Prototypes<br />Second generation prototype<br />Upload and download buttons did not relate to student audience. <br />Labels were clarified with ‘share’ and ‘find’ amendments.<br />Top-left navigation arrow did not match with user mental model.<br />Removed button as it did not match with user task flow.<br />
  12. 12. Reflective Review of Prototypes<br />Early android prototypes<br />
  13. 13. Thank you for listening<br />Please feel free to ask questions<br />