RequirementsFunctional

• Encourage social and cultural interaction through Culture Cow character.• Allow users to ‘feed’ and ‘find’ videos, recipes, stories and pictures for sharing.• Gain happiness points through sharing and rating content.• Users can request content based upon similar nationality, age or religion.

UserFun, inquisitive experience to form trust and a bond with the user.

Provide refreshing interface that addresses user engagement issues in University domain.

Usability Provide accessible and streamlined 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.

Non Functional

• Addressed lack of social communication: lack of ratings system, relevance / success of uploaded content.

• Religion vaguely discussed: making finding local religious groups part of the future planning, similar to Student Services.

• Limiting scope for negative social phenomena to occur: removing jokes, negative rating and functionality for moderation of content.

• Keeping anonymity important to the app: whilst increasing social interaction the app still keeps content and profiles private whilst still allowing users to be moderated.

Feedback

Scenario

• He searches through his university website for help with integration into Bristol social life.• He comes across the Culture Cow website and decides to check the url on his iPhone.• He registers and then logs into the app.• From here he uploads a flickr photo as it is the first logical step on the app.• He then searches for photos from other Spanish students and attempts to socialise with them

after rating a few of the photos.• He feels happier after realising there are other Spanish students in Bristol and hopes that he

can meet up with some of them.

• Carlos is an 28-year old male who has recently moved to Bristol to complete his masters degree in European Philosophy.

• Carlos is Spanish and this is his first time in England.

• Providing a succinct amount of options upon loading• Introduction of branding• New users call to action is present first

• Most important fields shown first• The order of the fields matches the user’s mental model of registering• Consistency between ‘call to action’ buttons• Back button present for users who misclick

• Split from other register form to reduce cognitive load• Drop down arrows provide affordance to suggest further options• Drop down boxes allow users to quickly progress through registration.

• Confirmation or error messages displayed.

• Familiar and universal login screen format.

• Keyboard space taken into consideration with menu.

• JQuery Mobile and iPhone defaults show completed formWhilst displaying login button and keyboard.• May prevent input errors before continuing process.

• Simple button to guide / aid user flow through application.

• Consistency with other applications, providing options in top-right and using cog icon.• Icons useful for users with English as second language.• Explanatory text that is succinct.• Call-to-action buttons easily recognised and prevalent.

• Consistent icon-based approach to free cognitive load and add character.• Question incites appropriate response via buttons.• Minimal interface to engage user; moving away from stagnant, desktop applications.

• Offering options for both novices and those with technical experience.• Flickr NSID code can be used as an ‘accelerator’.• Icons relate to real-world experience; searching and photography.• Division line splits two possible options.

• Shows an adequate number of results in a simple format.• There is enough space around the photos to allow for touch-screen interaction.

• Question allows user to confirm action or choose another.• Testing showed that photo selection can be tricky on touch-screen devices.

• Immediate feedback, notifying user of system process and consequential happiness change.• Light-hearted photo reflects application character.

• Consistent menu, identical to feed menu: recognition rather than recall.

• Limited options to streamline process.• User will recognise similar interface from registration.

• Results based on most recently updated photos, so they will change with each use.

• Recognisable rating system .• User choice to go to the home screen or rate the picture: contributing to the community.

• Light-hearted image is consistent with happiness.

Options• Help should always be available• Language and privacy integral to main requirements.• Users can edit their profile information.• Logout option differentiated from others. Top of the menu as it will be commonly used.

• A run through of all features in the current app prototype.

• Completed using wifi connection and iPhone 4.

• Some of the hi-fi features were not implemented in thisprototype.

• Design specifically for Android handsets

• Incorporate good Android design

principles

• Research Android applications

• Experience with Android systems

• Competitor analysis

• Approach helped futher design decisions

• Will allow for higher usability due to

increase in number of devices that can

access application

• Further implementation would have

helped finished application

Adopted Approaches 2

• As well as adhering to mobile (iPhone) design guidelines and principles, we also set out to develop and adhere to our design guidelines and principles.

• This allowed team members to develop elements of the application and also provide consistency throughout the application.

Adopted Approaches 4Carl’s Adopted ApproachDeveloping the lo-fi prototypes into hi-fi• My approach aimed to transform usability criteria and iterative lo-fi prototypes into hi-fidelity mock ups.• Usability criteria included: simplicity, navigation, error-handling, comprehensibility and efficiency.• Initially, I worked alone on shaping hi-fidelity prototypes from lo-fi examples.

Developing hi-fidelity prototypes alone neglected a balanced view.

Designing for the iPhone format withoutconsidering development platform implications.

Compromising original lo-fi design patterns to fit JQuery Mobile conventions.

Attention-to-detail ensured design guidelineswere followed.

.

Familiarity with Culture Cow requirementsbuilt on successful lo-fi iterations.

Efficient hi-fi process on Photoshop with elements altered to suit screen estate.

Facebook used for group communication.

Wordpress blog used to host research and develop ideas.

Development area used to prototype App ideas.

Team Communication

Helped to ensure version control.

Faster team communication and development.

Login restrictions to development area.

Harder to translate paper based design.

Evaluation

Design principles carefully considered, and user flow is simple.

Could integrate well with student services and local religious groups: could boost user base and support.

App has potential, and the idea has never been fully explored, with regards to International student support.

Branding and overall feel is professional.

Difficult to integrate and maintain anonymity whilst providing communication between users.

Jquery Mobile (in alpha stage) limited prototype opportunities. Compromised interaction ideas.

Difficult to ensure user comprehension with technical aspects.

App options were limited, lacked social awareness, taking away from the user experience.

• Rewards/Achievements system

• Develop as a native app for specific systems and

devices

• Develop a closer working relationship with student

services to ensure optimal sustainibility and

inclusiveness

• Enable linking between local religious groups and

Culture Cow users.

• Further user testing and usability promotion using

incremental changes

• A communication system between users such as a

chat or group-based collaboration

• Further integration with emergent Web 2.0

technologies.

• Adding moderation before content is made

available to the Culture Cow users.

Future Planning

Thank you for listening

We would be happy to answer any questions that you have.