AIP - Compliant Food Search
TEAM:UX Designer & Software Developer
MY Roll: UX, UI, IxD
Embarking on a new way of eating can be challenging for many, with many pitfalls along the way. How can we help users maintain and succeed on their new diet?
What we wanted to learn:
What were the biggest pitfalls to success?
What was the motivation for starting this diet?
How people were measuring success or failure?
The goal of my initial research was to learn what difficulties people were facing while on the AIP diet to determine what might make this diet easier to maintain. I also wanted to know what methods they were already using to learn about the diet and to track their success or struggles.
I received 286 overall responses to the Facebook survey questions and conducted 8 user interviews.
Many users did not know there were various versions of the diet.
The most followed version was created by Dr. Sara Ballytine
The most common question asked by all users, “Is this compliant?”
In the Facebook group, another common question was “What do you eat for breakfast?”
For those in the re-introduction phases, their questions were:
1. How do I start re-introductions?
2. “How do I know if I’m having a [negative] reaction?”
Imagine walking into a grocery store, a thing you’ve done a million times before, only to find yourself confused about what you suddenly can and can’t eat. Foods that were previously considered “healthy” aren’t actually good for you. The aisles filled with your favorite goodies are now off limits to you, Frustrated, you think “What can I eat on this diet?!”
After speaking with the users and reading their stories and needs, I listed the features/needs the mentioned and went to my developer. Together we did a Feature Matrix to decide which features should be worked on immediately and which ones could be save for later versions.
This User Flow maps out the primary actions a user must take to accomplish the three goals of the app.
Search if a food is compliant or not.
Search and save recipes.
After the final round of sketching I felt confident in moving on to some low fidelity wireframes. This allowed me to more carefully see the basic layout of the app to this point. I was also able to perform further user testing by making a clickable prototype using Marvel. I made necessary changes as I learned more about the users needs.
High Fidelity Wireframes
Click image to view Version 2 of the prototype.
This prototype shows the user as they:
Choose their phase
Perform their first search
View available recipes
What I Learned
Working with a developer has taught me the importance of keeping them in the loop as the project progresses. The developer I worked with was able to guide certain app features due to their viability and time constraints.
Many times we had to control the urge to add more and more features to the app. Keeping the MVP in mind helped to confine the first version to the most important features. Other features can always be added later.