...
We also realized that this application would be most useful as a mobile app. Originally we planned for LunchBunch to be an internet site, so we had a lot of information per page (especially on the “Create New Lunch” page). When we redesigned the UI to be a mobile app, we had to be consistent about including buttons that prompt the user for a decision on the top of the screen (e.g. “Done”, “Attending”, “Not Attending”, "Confirm"). We also had to make sure that no page was too long because the user shouldn’t have to scroll much on a mobile app. That meant splitting up the lunch creation process into two screens: the first one asks for event details and the second allows the user to invite people. As a result, each screen contains approximately the same amount of information and fits on one screen. We also made it easier to create a new lunch by just clicking on the “+” icon at the bottom of the list of lunches on the “Lunch Invites” and “Lunches I’m Attending” screens.
Because we turned LunchBunch into a smartphone app, we replaced the email reminder/confirmation request with a push notification that pops up on the phone. We also simplified the confirmation request to come along with the reminder so that users aren’t receiving two different types of notifications at different times. After the second iteration, they will either receive a reminder or a reminder with a confirmation request. Clicking on either type of notification will take the user to the event details page for that event but if a confirmation was requested, there will be a “Confirm” button at the top of the screen.
We stopped asking users to check for a conflict with a new lunch invite as a part of their tasks because we considered the fact that users will mostly be using this app to create lunches that are at most 2 days away. Most lunches between co-workers and students are planned the day before or the morning before the lunch. Thus, it's unlikely that conflicting lunches will be a problem for the user that the UI needs to take care of. Instead of better indicating a conflict on the "Lunch Invites" screen, we plan to show them a message if they accept a lunch that conflicts with another lunch in the "Lunches I'm Attending" list. However, most people know their short term plans and would most likely already have an idea if they have a conflict or not. Also, the easy navigation between the "Lunch Invites" and "Lunches I'm Attending" pages makes double-checking lunch times easy enough for the user.
As a result of the changes we made, the second iteration of the paper prototype was much simpler and easy to navigate than the original design. This simplicity makes the UI very appropriate for a smartphone app.