...
Our computer prototype can be accessed at the following website:
www.example.comPK3k's outfit.me
From this page, you should be able to create an account or , log in, and then perform all of the major tasks outlined below. Experiment with the website and attempt to take advantage of all functionality it offers. The tasks below are the ones we have focused on including in the breadth, but this is still a prototype - additional functionality, where needed, is still an option.
...
Background and Task Information
Background
Placeholder One (Brief description of the website and its purpose)PK3k has endeavored to design a product for users who are fashion-conscious (that is, those who want to look a certain way for a certain event), but are unsure of how to build outfits. Anyone who has looked in their closet, wondering "what should I wear?" will find an accessible community in PK3k's outfit.me. Our website connects those people who don't know how to build outfits from their wardrobe with like-minded, fashion-conscious people who can offer suggestions on how to build an appropriate outfit for any event.
Uploading the Wardrobe
Placeholder Two (This task is presently limited to only-online, for simplicity of design and interest in delivering a single, accessible project)Uploading your clothes to your account's personal wardrobe is presently handled solely on the website. We intend to extend this element of our application to also interface with mobile devices, but as this is a peripheral concept rather than a core concept, it was omitted from this prototyping stage.
Requesting Advice
Placeholder Three (This is a task users should be able to perform, open and free-form (all user-generated content here)).
Browsing Requests
Placeholder Four (This is a task users should be able to perform, from testing users or from our canned requests).
Creating an Outfit
The requesting interface presently is a one-step process, asking for both a question (i.e., title), and details about the question (specifics about location, season, expectations, and so forth). Additional potential functionality here is the inclusion of tags, and suggested clothing items that the user would like to build around (i.e., "I have this great gray sweater, but I don't know what to put with it...)
Browsing Requests
Requests are presently browsed from a single list of requests, each of which includes the question & details, the user requesting advice, and already-provided suggestions if there are any. We would like to extend the ability to filter this list, so you can look at only those requests pertaining to formal events, for instance.
Additionally, clicking on the name of a user from this page will bring you to that user's personal page, listing only those requests that user has posted; the user's wardrobe will also be displayed for reference.
Creating an Outfit
Outfit creation is implemented with a drag-and-drop interface and an additional comment window. Sorting the wardrobe here works the same as when articles are being added to the wardrobe. You can also re-read the user's question by hovering over the prompt at the top-left, which displays an overlay with the question and detailsPlaceholder Five (This is a task users should be able to perform, using canned wardrobes).
Browsing Responses to the Original Request
Placeholder Six (This is a task users should be able to perform, but note that we won't be automatically generating responses to our testing users' request, so they may have to explore other, canned answers)Responses are presently displayed in-line with the requests on the main page. This is a design decision we are investigating - do the responses need their own page, or can they be handled in-line on the same page? The current interface feels lighter in weight, which is nice for quick response. It does make evaluating the relative worth of responses somewhat more difficult, however; giving each request an individual page generated a much heavier, deeper call-and-response structure on feedback to outfit creators.
Additional Information
For more information on the purpose vision and directive objective of our project, you can read our updated User and Task Analysis page. For some examples on expected interactions with our website, you can read the Scenario on our Scenario and Designs page.