Interaction Design

A1 PresentationCulture Cow

Key Functional Requirements• Encourage user interaction through tamagotchi

character.• Allow users to upload and find videos, recipes, stories

and pictures for sharing.• Control tamagotchi’s happiness through uploading or

downloading.• Users can request content from users sharing mutual

nationality, age or religion.• Support potential user growth with register / login

feature

Key Non-Functional Requirements

User• Fun, inquisitive experience to form trust and a bond with the user.• Provide refreshing and exciting interface that addresses user

engagement issues in University domain.Usability• Provide accessible menus to users of all languages.Data• User data - email and password - will be recorded on a secure

database.Environment• Provide an interface that can be used in both a quiet or busy

environment.

Scenario - CarlosDescription:Culture cow sign up

Objective:Carlos needs to sign up for the culture cow application and configured the tamagotchi.

Background:• Carlos is a 28 year old student who has just moved to Bristol.• Carlos is Spanish and this is his first time in England. • He wishes to study and get a good grade and is worried it might be

hard to keep in contact with his family. • He has trouble making friends.

Scenario storyboard

Interaction Flow

Overview of interaction within the application.

Shows possible user paths

The way user actions affect the tamagotchi’s happiness

Lo-Fidelity Prototypes

Reflective Review of Prototypes

Reflective Review of Prototypes

Early paper prototype

Lack of affordance for entering name and location details

Moved from underlines to boxes

Not refined for keyboard

Changed form size to allow for keyboard to slide up

Reflective Review of Prototypes

Early paper prototype

Overly technical jargon, media type was inappropriate for audience.

Simplified to icons rather than drop down box.

Options button changed to icon, a cog.

Movement away from language to universal symbols.

Reflective Review of PrototypesSecond generation prototype

Upload and download buttons did not relate to student audience.

Labels were clarified with ‘share’ and ‘find’ amendments.

Top-left navigation arrow did not match with user mental model.

Removed button as it did not match with user task flow.

Reflective Review of PrototypesEarly android prototypes

Thank you for listeningPlease feel free to ask questions