hitched - GR4 Computer Prototyping

Group Members 

• Stephen Suen ssuen
• Kathy Fang kfang 
• Yi Wu wuyi
• Connie Huang connieh
• TA: Katrina Panovich

GR1 - User and Task Analysis

GR2 - Designs

GR3 - Paper Prototyping

GR4 - Computer Prototyping

GR5 - Implementation

GR6 - User Testing

GR4 - Computer Prototyping

Application Requirements

You will need a PC or Mac to use hitched on a web browser. Please use Chrome in full-screen to view and test the application. 

Accessing with Chrome

Please access the following URL: http://ssuen.scripts.mit.edu/hitched/

Shallow Parts of the Prototype

On all of our pages, you may interact with the UI, but your responses are not stored in the backend. Below is a list of shallowly implemented components:

Login/Register

• Login credentials are not stored in the backend. From the landing page, simply click on the "Sign in" button on the navigation bar (with any credentials) in order to login and proceed.
• Registration credentials are not stored in the backend. Simply click on the "Sign up" button (with any registration information) in order to register and proceed.
• The events that the user chooses to include in his/her wedding are not stored in the backend and are thus not displayed in the timeline.

Navigation

• On the navigation bar, the name of the person logged in is canned - "Tiffany".

Dashboard/Timeline/Settings

• The number and content of the new notifications are canned. The new notifications link to a canned event page for "Contact Photographer".
• The settings chosen by the user (i.e., password, date of wedding, wedding party email addresses, etc) are not stored in the backend and are thus not displayed or updated.
• The events on the timeline are canned, including the details displayed when the user hovers over an event.
• On the timeline, when the user hovers over any event and clicks the "View event" button, he/she is brought to a canned event page for "Contact Photographer".
• Dragging events on the timeline to change the event date is currently unimplemented, as is scrolling.
• Filtering is only partially implemented---you can disable categories but cannot bring them back as of yet.

Events

• On the event page, the name of the event ("Contact Photographer"), location, time, date, description, and previous comments are canned.
• Any edits that the user makes to the event's location, time, date, and description are not stored in the backend and are thus not updated.
• If the user submits a comment, then the comment is displayed on the event page as long as the page is not reloaded. Comments submitted by the user are not stored in the backend.