...
| Charles opens the Next Ride website and enters his name and number and hits ok. This is simple, learn-able and difficult to screw up. This would be slow to do every time, however if this information is stored in a cookie it should be efficient in that it is only done once. |
| This brings him to the main page which defaults to the “To Campus” tab. He can see the Date at the top, and the current hour is blown up in detail at the top of the scroll pane. He looks at the times between 11am and 3 and sees that 2 people are requesting a ride at 2. He clicks on the 2:00 time block and a menu opens up. This UI sacrifices learnability for efficiency. It is not immediately obvious that the times, cars and 'requests' are clickable. However, the display packs in a lot of information that is easy to parse quickly, and requires only a single click to get to the schedule menu. |
| The schedule screen allows Charles to schedule a ride. He chooses the type of ride (car), the number of spots (4) and the time (which defaults to the selected time 2:00pm). In order to help charles choose a specific time requests near the selected time are shown. He can choose to recieve SMS notifications (for when people join/leave his ride). He then clicks ok. This UI has a number of clearly labelled fields which can be edited which is easy to learn. The defaults allow the user to get through the UI quickly. The immediate feedback in the UI provides safety and the user can always click cancel if they didn't intend to schedule a ride. |
| This returns Charles to the original screen where he can see that his car has been added at 2:00pm with 4 seats. This gives the user immediate feedback about their action. |
Task 2 (Alexis)
| 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. |
...