...
- It’s 11am right now. Jorge is at the house and needs to get to campus before 1pm. He doesn’t care when he goes as long as he gets a ride before one. Jorge wants to look at the available rides and reserves himself a spot on a ride at 12:30pm.
Observations
| Task 1 | Task 2 | Task 3
|
|---|
User 1 | - Splash page rather intuitive, he did not realize the times were clickablecould be clicked on
- Clicked on view schedule
- User loged logged in no problem
- First user was very confused on the schedule page (no ride and request headers)
- Was not super confident but ended up clicking on the left side to create a ride.
- Offer page was intuitive flew by no problem
- When asked to find his offer user tried to click the offer he created but that spawned a reserve page (this was duly noted)
| - Again no problem with splash and main schedule page (especially since we added labels between the different user tasks)
- User was slightly unsure if the cab was an offer or request, however , he ended up creating it as an offer.
- Since he had already done task 1 he flew by the page no problem (means efficeny efficiency is high)
| - Looking at request the user understood to click and drag on the right side of the screen ( we were very happy about this) this brought them up to request page and again the user did well.
- The rest went well.
|
- Wasn't sure if the number written inside the
| | |
| | |
| | | |
Prototype Iterations
Changes that occurred between the first ans second iterations are:
- Added icons to the times to make it more obviously clickable
- Added ride and request headers on the top of the schedule page, to signify what the different things were.
- Your rides/request/offers have a slightly different look
- Added the notes section to allow for input of additional information when offering or requesting a ride