Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Task / Design Images

Storyboard

Usability Analysis

Uploading wardrobe

In order to upload his wardrobe, Sylvester uses the mobile application.  He registers using the mobile application (he could have also done so directly on the website).  Upon signing in, he is brought to the page where he can choose to a) add clothing to his wardrobe b) request advice on the website c) view requests he has posed in the past.  He chooses Add Wardrobe and is immediately brought to the phone's proprietary camera interface.  He takes a photo of an item of clothing, and is brought to a page with a thumbnail of the image and the option to accept or retake the photo.  If he chooses accept, he is brought to a screen where he can tag the piece of clothing.  At the very least, he must use the visual icons to tag the type of article of clothing (t-shirt, dress, shoes, etc.).  He also has the option to add verbal tags that describe the article of clothing in more detail (purple, striped, etc). If he chooses to retake the photo, he is taken back to the camera screen.

**Wardrobe Usability goes here**

Posing a request

After adding clothes to his wardrobe and selecting 'Done', Sylvester is brought back to the menu page where he selects "Ask for Advice".  He is brought to a simple page in the application where he can ask a request and provide details. Sylvester fills in a request for advice and a few details about his target girl and upon hitting "Submit," Sylvester's request is immediately posted to the website.

**Pose Usability goes here**

Browsing requests


(Note: This interface is the same as in Design 1. The storyboard is copied here for better readability)
Felicity and Sylvester visit the homepage.  They see Sylvester's request at the top of the list under both the "Friends" and "Everyone" tabs (for Sylvester his is also shown under the "Me" tab).  Felicity  

(Note: This interface is the same as in Design 1. The storyboard is copied here for better readability) 
Felicity chooses his request and is brought to a page where she can see recent comments and outfits, and is presented with the opportunity to comment as well as create a new outfit. Here, Sylvester and Felicity can up and down vote different outfits that have already been created. (Note:  The top request in the mockup above is a request about a wedding.  In this specific scenario, the request would be posed by Sylvester and be about his date outfit). 

**Browse Usability goes here**

Creating an outfit

Felicity selects "Answer" on the comment page, and is brought to the outfit select page.  There she is able to add items to the wardrobe.  When she selects "Add Item", a window pops up where she is able to filter Sylvester's wardrobe using visual icons.  When she selects an item, she is then brought back to the wardrobe assembling screen, where she is able to directly comment on each article of clothing to explain why she chose it, how it should be worn, etc. This differs from the first design in that the item cannot be physically manipulated on the screen.

**Create Usability goes here**

Browsing a response to a previous request

Sylvester gets a notification on his phone and notices that several people have suggested outfits for him.  He uses the mobile application to open up his list of previously asked personal requests, and selects the request about how to impress the cute girl.  He scrolls through the items in the outfit created by his friend Felicity by scrolling up and down. By scrolling left and right, he can view other outfit creations by users he has never met.

**Personal Browse Usability goes here**

...