User Tests

Complete the main flow: Get a Bike

~2 min

35, Male, Sofia Resident
Graphic Designer | Active Biker

• No assistance needed
• Every step passed on the first attempt

• No Availability icon is confusing
• Reservation expiry time is unclear
• Payment rules are unclear

Complete the main flow: Get a Bike

less than 3 min

27, Female, Sofia Resident
Front-Ender | Not a Biker

• Sliding to reserve is clear enough - worked out instantly
• Availability is clear enough

• User expects functional input fields
• User expects faster prototype response
• User expects pagination indicator to be fully functional
• User expects pinch zoom to be functional

Complete the main flow: Get a Bike

30, Male, Sofia Resident
Financial Officer | Casual Biker

• Sliding to reserve is clear enough - worked out in 12 sec
• Availability is clear enough

• User expects functional input fields
• User finds it hard to visualize the test situation and connect scanning bike's QR-code with unlocking the bike
• User struggles with prototype's slow response

• Complete the main flow: Get a Bike
• Secondary flow: Add a Payment Method

• Get a Bike: ~3 min
• Add a Payment Method: ~1 min

30, Male, Sofia Resident
Designer | Not a Biker

• Sliding to reserve is clear enough - worked out instantly
• Availability is clear enough

• User struggles with non-functional input fields in the prototype
• User expects to be able to drag the map of the prototype

• Complete the main flow: Get a Bike
• Secondary flow: Return the Bike

• Get a Bike: ~3 min
• Add a Payment Method: ~1 min

29, Female, Sofia Resident
Traffic Engineer | Not a Biker

• Sliding to reserve is clear enough - worked out instantly
• Availability is clear enough

• User struggles with non-functional input fields in the prototype
• User expects to be able to drag the map of the prototype