top of page
NOOCH
MOBILE APP
-
Competitive analysis
-
User research and interviews
-
Storyboarding + Personas
-
Low and hi-fidelity iterative prototyping
-
Collaboration
-
Usability testing
-
Figma
How might people with dietary restrictions grocery shop confidently?
Overview
60% of US households consist of at least one individual with a dietary restriction, often making grocery shopping a daunting task. Nooch (short for nutrition!) aims to increase nutritional literacy for those with dietary restrictions. By scanning nutrition labels to evaluate alignment with dietary needs or find viable alternatives, users can have a stress-free grocery shopping experience, remaining confident their needs are met. Nooch allows users with dietary restrictions to scan the label of a product while grocery shopping to evaluate whether it aligns with their dietary needs, find suitable alternatives, and learn more about each specific ingredient in a product and its health implications. By filling out a one-time specific nutritional profile with detailed dietary information, users can rest assured their nutritional needs are being met every time they shop without having to do extensive research beforehand.
The Problem
There is a severe lack of nutritional transparency and literacy surrounding ingredients on food labels, making decisions when grocery shopping especially confusing for customers with dietary restrictions.
Objective
Design an application that will allow for increased nutritional literacy and provide viable alternatives for ingredients and products.
Research Process
Exploring the Problem Space
In order to better understand the problem space, I used the research methods of competitive analysis and user interviews. From these two methods, I was able to collect data about user needs and frustrations that could then be applied to deliverables.
1
Competitive Analysis
Analyzed four different nutrition scanning app competitors of varying types, from direct competitors to analogous competitors, and identified several pros and cons of each. From this analysis, I was able to identify several factors to avoid in my app as well as features to include. It also helped me to get a better idea of how saturated the nutrition app sphere is, and how to create a niche that is still valuable to consumers.
2
User Interviews
Interviewed users based off of a predetermined interview script with semi-structured questions such as 'Do you ever have trouble finding foods that fit your dietary needs?' and 'How do you plan your trip to the grocery store? (Do you have a planned out
shopping list? How well do you usually follow your list?)'. These interviews allowed me to identify three themes across participants: difficulty
fulfilling health goals, high reliance on
nutritional value and ingredients, and getting diet suggestions from external sources.
Deliverables
Feature Ideation
From the insights gathered in my user interviews and competitive analysis, I was able to create a series of ideation sketches envisioning how the solution could be implemented according to user needs.
User Personas
Another set of deliverables I was able to create from the data collected were user personas. Each user persona encapsulates the motivations, frustrations, and behaviors characteristic of a specific type of target user of the application. The persona walks through a user's motives, behaviors to try to achieve those motives, and blockers or frustrations when achieving goals, in order to identify pain points and needs.
Storyboarding
With the data collected from user interviews and the persona development, I was able to create a storyboard outlining a current issue and need through a scenario. This storyboard helps to demonstrate the need for the target user population in a more contextualized setting.
Iterative Design Process
01
Ideate
Develop ideas for solutions based on data from user testing, research, and needs assessment.
02
Prototype
Bring the ideas to life through design and create interactive prototypes that convey the idea's main elements.
03
Feedback & Test
Test your designs with target users to identify pain points, confusion, and issues that must be addressed.
Design Process
User Flow
Once I had established the target user's motivations, pain points, and goals, I began to map out the various screens and features that the app would contain to get a visual of how the app would function and flow and whether the organization of different tabs and sections made sense.
Low Fidelity Prototype
After tentatively defining all of the features and screens of the app, I mocked up initial versions of all of the main app screens to visually map out where things should be placed. I focused on the main screens of the app in order to have enough to test functionality later on.
Usability Testing
In order to test the effectiveness of my design, I gave my main app screens basic interactive functionality using Figma. I then conducted usability testing with several participants using this paper prototype, noting where users became confused or got stuck, and what features they found intuitive or enjoyed below is an example of the usability log used for the test as well as a video walkthrough of the prototype.
Digital usability test walkthrough with lo-fi prototype
Hi-Fidelity Prototype
After several rounds of iteration with the low-fidelity prototypes, I was ready to move on to more hi-fidelity designs in Figma. Below is the process and progress I made with developing my final app deliverable, being sure to test and adjust the design along the way.
That's all, thanks for following along!
bottom of page