-
Notifications
You must be signed in to change notification settings - Fork 1
Phase III
In Phase III, we tested our Allergy Detect prototype to see how well it worked for real users. Our goal was to learn whether people could complete the main tasks, understand the allergy results, and feel confident using the app. We focused on finding problems in the design before making final improvements. This usability evaluation helped us see what parts of the app were clear, what parts were confusing, and what changes would make the app more useful for users.
We conducted a formative usability test of our prototype, Allergy Detect. This means our goal was not to prove the app was perfect. Our goal was to find what worked well, what confused users, and what changes would make the app easier to use.
The test was moderated, meaning one team member guided the participant through the session. We also used a think aloud method, where participants were asked to say what they were thinking while using the app. This helped us understand what users expected, what felt clear, and where they got confused. The protocol told participants that this was not a test of them, but a test of the app.
We tested the prototype with 4 participants. Participants had different levels of experience with allergies and checking food labels. Some participants had allergies, while others did not. Most participants said they usually check food labels manually when shopping. The main material used in the study was our mobile prototype for Allergy Detect. Participants completed three main tasks and answered follow-up questions after each task.
Task 1: Scan/find a safe product
Participants were asked to find a chocolate cake without peanuts. This task tested whether users could understand the scanning flow and use the app to decide if a product was safe. This mainly tested learnability, efficiency, and task success. The follow up difficulty and satisfaction questions helped us understand how easy and satisfying the scanning process felt.
Task 2: Set up an allergy profile
Participants were asked to set up a child’s profile with a gluten restriction. This task tested whether users could find and use the profile setup feature. This mainly tested navigation, flexibility, and whether the profile options matched user needs. We wanted to see if users could easily find and use the profile setup feature. This helped us understand whether the app’s navigation made sense.
Task 3: Interpret scan results
Participants were shown a product result and asked what they thought it meant. This task tested whether users understood the result screen, especially the safe/unsafe message, colors, and ingredient information. This mainly tested clarity, confidence, and trust. The follow up questions asked what information was most useful and what was missing or unclear. This helped us learn what parts of the results screen should stay and what parts need improvement.