...
| Alexis gets the same landing page as Charles |
| Alexis is then taken to the main page where he selects the "To House" tab. He sees that nobody is driving to the house anytime soon. The current hour is expanded, and he wants to leave in half an hour so he chooses the 2:30 time to make a request by pressing on the '-' |
| This bring up the request menu. There are only a few options here: time, type and number of people all of which are clearly labeled and use standard input methods. This is very learnable, and with proper defaults can be very efficient. If Alexis has made a mistake he simply cancels. |
| Finally Alexis is returned to the main page where a "1!" has shown up in the requests column to give feedback that his request was accepted. |
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 |
...