...
Errors: Users will have the option to delete items that they don't want from their order, as well as the option to back out entirely. Essentially, one can undo any action up until the time that the order is submitted. If this design goes without a chat box entirely, the users may run into a communication issue if the interface doesn't take into account every desired communication. For example, Janet could have ordered half the duck, but Tim could have clicked the “other half” button first, leaving Todd still wanting to share the duck. In this model, without the chat box, there would be no way for Todd to communicate to Tim that he specifically wanted to share the duck with Janet (ie optimizing food order could be tricky).
Design 2: 
- William wants to invite his friends into an order. He logs in to the page through Facebook connect, and is brought to the create order page. Here he is able to type in his friends' names (with suggestions provided by facebook), as well as the e-mail addresses or phone numbers of other people he wants to invite to the order. Once he he has selected at least one friend, the arrow leading to the next box lights up.
- Here he is able to choose the restaurants he wants to seed the list with, and can search by name (with suggestions provided via foodler) and in addition filter these by category and price. Adding one or more restaurants lights up the arrow for the next box.
- The Get Started box holds a large "Send!" button and a box to enter an optional message.
- Content in any of the boxes can be modified at any stage until the form is sent out.
- Heather receives the e-mailed link from William, and deciding that she's up for Thai food, clicks it. She is automatically identified by the unique url.
- She chooses which restaurants she wants to order from, and briefly thinks about suggesting somewhere else before deciding that Pepper Sky is good enough for now.
- William, when everyone has finished, clicks the selection button for the restaurant. The arrow heading to the next box lights up, indicating it's time to order.
- Heather, seeing this, clicks the view menu button, which brings up a floating div containing the restaurant menu in a foodler-style format. This menu allows her to view prices, select special options, and specify if she would want to split the meal or eat the whole thing.
- The menu dynamically updates to show the selections of the other users, and indicates the split/full status of each item.
- At any time, the user can remove an item they've selected.
- When Heather is done ordering (having decided to just save some of the rice for later), she clicks the done button at the bottom of the frame.
- After everyone has done so, William brings the Order to completion.
- Once this is complete, Heather is brought to this screen, informing her how much she owes, and to whom.
- She will also receive an e-mail when the order arrives, reminding her of how much she owes. The e-mail will use dynamically created images and HTML to show the status of their payment.
General Comments on Design 2:
Learnability: To start up an order, it is quite natural for people to search through list of Facebook friends, as everything is connected to Facebook nowadays. In addition, the general ordering interface will be very similar to that of Foodler (and can be used exactly as such at a base level). Our interface will simply provide simple add-ons that people can choose to use (“me too” “I want to share”). In addition, payment will be the same as usual for online food ordering.
Efficiency: Linking up to Facebook will allow suggested completions of names, as will providing a list of restaurants. This will help organizers suggest things quickly and easily. Selecting restaurants will be facilitate by filter options embedded in the menu (“want” “do not want”) next to restaurants and food types. In addition, allowing people to order simultaneously cuts down on menu reading time and allows for more instant feedback regarding choices.
Visibility: This interface prioritizes important things, including showing a list of people included in the order as well as constraints imposed upon restaurant selection. Showing the constraints allows the user to know whether or not a certain restaurant will be “allowed”. In addition, familiar “vote up/vote down” buttons will perform the obvious action of showing the other users a list of preferences in the right pane.
Errors: Users will have the option to delete items that they don't want from their order, as well as the option to back out entirely. Essentially, one can undo any action up until the time that the order is submitted. If this design goes without a chat box entirely, the users may run into a communication issue if the interface doesn't take into account every desired communication. For example, Janet could have ordered half the duck, but Tim could have clicked the “other half” button first, leaving Todd still wanting to share the duck. In this model, without the chat box, there would be no way for Todd to communicate to Tim that he specifically wanted to share the duck with Janet (ie optimizing food order could be tricky).