ahandrewh teaches IAT-334interface design

P1: Features (due June 8/June 10)

On this page:

This is old content

Andrew is not currently teaching IAT-334. This material is left online for reference only.

Introduction

Research is key to understanding the context and users we are designing for. For this project you will design a new feature for an existing mobile application. This will require researching the existing interface, interaction patterns, features and users.

This project is completed individually.

P1: Features is worth 10% of your final grade.

Applications permitted

The following applications are permitted for this project.

If you have another application that you would prefer to work on please email Andrew before May 18 to discuss.

Weekly instructions

This project spans multiple weeks. Please read the weekly instructions carefully.

From May 18 to May 27

This week is for completing some exploratory and evaluative research on the chosen application.

For the exploratory research we are looking to understand the purpose of the application, its users, and their goals for using the application. For the evaluative research we are looking at the usability and design patterns within the application.

Please complete the following:

  1. Explore and investigate the interface as it is now. Capture and document in screen-shots, sketches, and/or notes:
    • The primary purpose of the application
    • Key features (pick two)
    • Interface design patterns, or what does it look like? (colours, icons, type, layouts, etc.)
    • Interaction design patterns, or how do we move through the application? (clicks, swipes, scrolls, etc.)
    • Intended users
  2. Having identified intended users, find two intended users and evaluate with them:
    • What is their familiarity with the application or similar sorts of applications?
    • What is one feature they use most often? Have them step you through how they typically use this feature.
    • Does anything about that feature frustrate them? If so, why?
    • What (if anything) do they appreciate most about the feature? and why?

Assemble your research into a document that is designed for easy and concise understanding that answers the questions above. The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

Bring to your May 25/27 lab

A document (PDF, website, etc.) containing:

  • Your interface exploration
  • Your two user evaluations

We will chat about your deliverables in-lab.

From May 25 to June 3

This week is about generating ideas for a feature.

  1. Working from your research, consider what kinds of new features would make sense for your application? You are coming up with two different options. Be prepared to answer:
    • What is the new feature?
    • What goals does it help your user achieve?
    • Why will it work for those goals?
    • Why should we care about it?
    • How might it work?
    • How might the user interact with it?
  2. Generating ideas may result in further questions. For example: "How might the user interact with it?" may be difficult to answer without some further insight from your users. Go back and do more exploratory or evaluative research as needed to support your case.
  3. Create and illustrate a scenario for each new feature. These can be done as a storyboard, sketched wireframes, or a combination of the two. The scenario should illustrate:
    • Why the user would be making use of the new feature.
    • In what context the new feature would be used.
    • Where the new feature is situated in the application overall.

Assemble your new feature proposals into a document that is designed for easy and concise understanding that answers the questions above. The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

Bring to your June 1/3 lab

A document (PDF, website, etc.) containing:

  • Two proposed new features with explanations
  • Two scenarios (one for each new feature)

We will chat about your deliverables in-lab.

From June 1 to June 10

This week is for building an interactive prototype of one new feature.

  1. Based on feedback from the labs, choose one new feature and create a complete interactive mockup for it. The tools you use are up to you, but the mockup will need to:
    • Show a graphically polished and complete version of the new feature.
    • The series of displays related to the feature.
    • Make use of the application's existing visual language.
    • Make use of only real text (no placeholder text).
  2. Create an updated scenario using the interactive mockup. The scenario can be presented as a video with voiceover (maximum 2 minutes), a slide deck with annotations, or a webpage with explanations. This scenario needs to answer why and how this feature is fulfilling a user need.

Assemble all project materials (from May 18 to June 8/June 10) into a document that is designed for easy and concise understanding. The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

You are allowed to improve your earlier weekly deliverables for your final submission.

Grading rubric

Your project will be graded on the following criteria:

A B C D/F

Reasonably concise writing (2 points): 'Can I follow the process? Does it stay on topic?'

The writing and supporting artifacts — i.e. images, quotes, process material, etc. — present an easy-to-understand narrative from start to end of the project without extra, un-related materials.

The writing and supporting artifacts — i.e. images, quotes, process material, etc. — present an easy-to-understand narrative from start to end of the project with some extra, un-related materials.

The writing and supporting artifacts — i.e. images, quotes, process material, etc. — present an understandable narrative from start to end of the project with some extra, un-related materials.

The writing and supporting artifacts — i.e. images, quotes, process material, etc. — present a confusing narrative of the project with materials that are not clearly related.

Interface design (4 points): 'Does this feature look and feel like the app?'

  • The designed feature provides an exceptional design — legible, clear hierarchy, excellent use of space/composition, interactions, and consistent elements.
  • The feature integrates seamlessly integrates with the existing application.
  • The designed feature provides an effective visual design — legible, clear hierarchy, excellent use of space/composition, interactions, and consistent elements.
  • The feature integrates effectively with the existing application.
  • The designed feature provides a somewhat problematic visual design — somewhat illegible, unclear hierarchy, somewhat ineffective use of space/composition, confusing interactions, and, or inconsistent elements.
  • The feature integrates somewhat effectively with the existing application.
  • The designed feature provides a ineffective visual design — illegible, unclear hierarchy, ineffective use of space/composition, confusing interactions, and inconsistent elements.
  • The feature does not integrate well with the existing application.

Effective argumentation (4 points): 'Would a client be convinced by this feature?'

  • The pitch explains why and how the feature is fulfilling a user need for a non-design audience.
  • Artifacts — images, quotes, process materials, etc. — used in the pitch make a strong case for the feature's usefulness.
  • Completed within two minutes.
  • The pitch explains why and how the feature is fulfilling a user need.
  • Artifacts — images, quotes, process materials, etc. — used in the pitch suggest this feature's usefulness.
  • Completed within two minutes.
  • The pitch somewhat explains why and how the feature is fulfilling a user need.
  • Artifacts — images, quotes, process materials, etc. — used in the pitch suggest this feature may be of use.
  • Completed in over two minutes, or under one minute.
  • The pitch does not effectively explain why and how the feature is fulfilling a user need.
  • Artifacts — images, quotes, process materials, etc. — used in the pitch do not support the need for the feature.
  • Completed in over two minutes, or under one minute.

Final submission requirements (June 8/June 10)

The final submission for P1 is a collection of all weeks of the project into a document that is designed for easy and concise understanding. The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

Your project submission is due to Canvas before your June 8/June 10 lab.

Please make sure double-check all your submitted files and URLs to ensure they can be opened. We want to avoid late or problematic submission penalties whenever possible.