...
Task 2 (Alexis)
Task 3 (Jorge)
| Jorge sees the same landing page as everyone else |
| Jorge is then brought to the main page which again defaults to “To Campus”. He sees that the only ride before 1 is in the 12:00 block, without scrolling down to see a more specific time he chooses that ride by clicking on it. This opens a reservation menu. Again, this UI is sacrificing learnability. It's not immediately obvious that the car icon is clickable, however Jorge can quickly see that the most fitting ride is the car at 12:00 and can select it with one click. |
| The reservation menu tells Jorge the name of the driver, the ride type and the departure time. He can then reserve up to 3 Seats. The screen also displays Yifan’s number witch icons which allow him to directly text or call. Jorge makes a selection and hits ok. Here the interface provides Jorge with additional information about the ride, and then allows him to pick a number of seats. This is learnable, and efficient. If the user doesn't want to reserve a ride they can simply cancel. |
| Jorge is then returned to the main screen where he can see that he has been added to Yifan’s car and the number of available seats has been reduced to 2. Again, the updated UI give immediate feedback to the user. |
Design 3
Task 1 (Charles)
Navigates to the Next Ride page and chooses the “Schedule a ride” option
The UI goes to the next page that lets Charles choose parameters for type of ride to schedule. He chooses the “to Campus” option and to schedule a car ride that leaves between 11:00am and
3:00pm. Then he clicks on Next.
He is then taken to another page that shows the ride requests in the time range he selected so that he can factor this information into his decision if he wants to. He sees that Pas2 and Pas3 want rides at 2pm so he decides to leave the house at 2pm. He clicks “Next”.
He then enters his name, contact info, number of spots and time in the final page and click on the finish button to complete the process.
...
Navigates to the Next Ride page and chooses the “Find a ride” option
The UI goes to the next page that lets Alexis choose parameters for type of ride to find. He chooses the “to House” option and that he wants a car, van or other ride that leaves from campus between 2:30am and 6:00am. Then he clicks on Next.
He is then taken to another page that tells him that there are no currently scheduled rides in the time frame that he chose in the last screen. He is given the option to choose different parameters for a search or to request a ride. He chooses to request a ride.
In the “Request a ride” screen, he enters his name, contact info, and he chooses the option to auto-reserve a spot. He then clicks on finish to request the ride.
...
Navigates to the Next Ride page and chooses the “Find a ride” option
The UI goes to the next page that lets Jorge choose parameters for type of ride to find. He chooses the “to Campus” option and that he wants a car or van ride that leaves to campus between 11:00am and 1:00pm. Then he clicks on Next.
He is then taken to another page that shows him two currently scheduled rides to campus in the time frame that he chose in the last screen. He then chooses to ride in Yifan’s car by clicking on it.
The next screen is for “Reserving a spot” in Yifan’s car. He enters his name, contact info, and clicks on the “Reserve a spot” button.
* Learnablity - Easy to learn because it is what you see is what you get
* Efficiency - Inefficient that you need to go through multiple pages to perform the action.
* Safety - He can always go back if he makes an error. You would need a different interface to cancel a requestreques