User testing Methodology and Key Findings

After making revisions to the hi fi prototype, we had the final interactive app on the phone and we started planning the evaluation phase. 

User testing plan

Our main objective in conducting user testing was finding answers to the following questions:

•     Is the application useful? Is it usable?
  
•     What feature are most useful? What features are unnecessary?
  
•     How easily navigable is the system? Are the interactions intuitive?
•     Is the app a time saver?
•     Do users have any wish lists?

We planned to test iteratively. After the first round, we wanted to redesign the app based on feedback and then test the app again.  We briefly outlined the tasks that we wanted to test in the first round. This included:

•   Testing the scanning of items into and out of the fridge.
•   Testing usability of the 'Fridge' screen - Can users tell when items are expiring? Can they reset expiration dates? Would they be able to find recipes easily? Can they access the shopping list readily? 
•   Testing the shopping list operations. 
  

Recruiting users:

Prior to developing the lo fi prototype, we had identified the key users of the application to be students sharing refrigerators and owning smart phones. We contacted students/ young professionals that we thought might be prospective users of the app and scheduled testing sessions with them.

User test methodology

The tasks were designed to take 10 - 15 minutes of the user's time. Before starting the test, the user was given a brief introduction to the application and the initial data entry to the desktop part of the app was explained. 

Task 1: On seeing that you are running out of milk, you add milk to your shopping list. 
The user was presented with the phone and asked to launch the application. The user was also given QR code for milk, asked to scan the code and add to shopping list.

Task 2: Check which items in your fridge are expiring.
The user had to identify items that were expiring and also check how many days were remaining before they expired. 

Task 3: Find recipes containing milk and pumpkin as recipes.
The users were given no instructions for this task.

Task 4: Assume you have finished shopping at the grocery store, you want to check the items you just bought into your fridge using the app (so that the app updates the status of these items accordingly). 
This task was to test the checkout feature form shopping list. We were interested in understanding if the users can find the appropriate screen and execute the task accurately. 

User testing results

Round 1:
Testing the app with users revealed that we some features were very useful as well as intuitive to use and there were some features that were not. We were interested in knowing what users were looking for and what they expected. Some key takeaways from the testing are listed below. The detailed user testing notes are available here:

• Scanning: An important finding when we tested for scanning was that QR codes cannot be scanned easily in dim lit rooms, and from a distance. It requires a good amount of light and for the user to be standing close to the codes.
• Checking expiry dates: Users expressed the need to see some sort of categorizing on the friedge screen. For example, one user wanted to see the items sorted by expiration date and another user wanted the the items to be categorized by type such as dairy, produce etc. This was extremely helpful feedback and we included this feature for our second round of testing.
• Finding recipes: Users showed a lot of interest in and enthusiasm about the recipe finder feature and it was also found to be very easy to use.
• Checkout from shopping list: A majority of the users we tested were slightly confused  with the 'checkout' feature and needed orientation. Proir to testing, we had changed the term 'checkout' to 'checkout to fridge'. However, it was still unclear to most of our users. 

Round 2:
Another round of testing was conducted after editing the design based on Round 1 results. The recipe finder continued to be a favorite feature while the 'checkout' feature has some scope for improvement. 


Videos of interactions can be found here and detailed results can be found here