...
The purpose of our application is to allow users to browse lunch invites, respond to lunch invites and create new lunches. For simplicity, we chose to limit the main navigation to two main tabs: "Lunch Invites" and "Lunches I'm Attending". Lunch Invites have 4 states: declined, accepted, confirmed(if it has been requested by the creator), and unknown(for those invites to which you have not responded. Accepted invites and subsequently confirmed invites appear on the "Lunches I'm Attending" page. Invites to which the user has not respond or has declined appear on the "Lunch Invites" page. Both these pages are set up as browseable lists. The user may click on a particular lunch to view its details. For this general design, the biggest gain from user testing was in the wording in our application. We went through multiple iterations of labels for the tabs and labels, eg. "joined", "my lunches", "unjoined", etc. before deciding on the set that made the most sense to the most users.
Figure 1: Image of the application when first Figure 2: Image of the Lunch Details page. Initially,
opened. a user may choose to "accept" of "decline" and invitation and
as the status of the lunch invitation changes, the buttons in the
top right hand corner will be modified accordingly.
Implementation
...