ahandrewh teaches IAT-334interface design

P1: Features (due May 29)

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 what we are designing for. In this project we will start by understanding an existing interface's patterns and features to enable us to propose a new feature for the interface.

This project is completed individually.

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

Interfaces permitted

The following interfaces are permitted for this project. If working with a digital application please select one device type to work with (i.e. phone, TV, smartwatch, etc).

If you have another interface for that you would prefer to work on please email Andrew before May 13 to discuss.

Weekly instructions

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

From May 8 to May 15

This week is for gaining an understanding of the features and patterns present in the chosen interface. Please complete the following:

  1. Explore the interface as it is now. Capture and document in photos, screen-shots, sketches, and notes:
    • The primary purpose of the interface
    • Key features (pick two)
    • Interface design patterns; what does it look like? (colours, icons, type, layouts, etc.)
    • Interaction design patterns; how do we move through the interface? (toggles, clicks, swipes, scrolls, etc.)
    • Likely intended users (based on your experience with the interface)
  2. Having identified each of the above, answer why you believe so. For example:
    • Why do you believe this is the primary purpose of this interface?
    • Why are the two features you selected key to the primary purpose of this interface?
    • Why are the items you identified actually patterns of the interface and interactions?
    • Why do you believe the users you have identified are the intended users?

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

Bring to your May 15 class

A document (PDF, website, etc.) containing the overview of the interface described above.

We will chat about your deliverables in class.

From May 15 to May 22

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 intreface. You are coming up with two different options. Write down:
    • 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 will the user discover and use the feature?
  2. Create and illustrate a scenario for each new feature using wireframes. The scenario should illustrate:
    • Where the new feature is situated in the interface overall.
    • What the feature allows the user to do.

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

Bring to your May 22 class

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 class.

From May 22 to May 29

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

  1. Based on feedback from class, 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 interface'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) or a webpage with explanations (maximum 300 words). This scenario needs to answer why and how this feature is fulfilling a user need.

Assemble all project materials (from May 8 to May 29) into a document that is designed for easy and concise understanding, maximum 1000 words overall. The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document. Cite any materials that are not of your own making.

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 existing interface?'

  • 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 interface.
  • 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 interface.
  • 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 interface.
  • 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 interface.

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 or 300 words.
  • 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 or 300 words.
  • 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; or over 300 words.
  • 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; or over 300 words.

Final submission requirements (May 29)

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. Cite any materials that are not of your own making.

Your project submission is due to Canvas before your May 29 class.

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.