top of page
Search
Writer's pictureKlarisse Talacay

FamilyCart: Solving common grocery shopping woes

Updated: Feb 25, 2021

Family Cart is designed as a collaborative app specifically for grocery shopping within a household. The design aims to solve common problems that a household encounters before, during, and after running grocery errands.


I. Personal Objectives

  1. Be able to design solutions for common problems of household members within the grocery shopping experience

  2. Be able to practice designing solution as I take on the role of a Product designer and UX designer

II. Identifying the problem


After a quick brainstorming with potential stakeholders, we have uncovered a few pain points


1. Items forgotten to be written down on the list because:

  • Verbally passed to the person responsible for grocery shopping

  • Members of the household forgetting about shopping day therefore they don’t get to list down what is needed in time

2. Incorrect variant/brand bought by the designated shopper.

3. Person responsible for the shopping forgets to update the household members about an item on the list not being bought.


III. User Persona an Scenarios


A. Personas:

B. Scenarios

Scenario 1


It’s 8:30pm on a Friday and each of the Porter family member has received a notification from their “FamilyCart” app reminding them that tomorrow at 10am will be grocery day and that they only have a few hours to list down what they needed to be bought. The eldest son, Dennis, proceeds to check how many protein bars he has left in the pantry. He decides he needs to replenish his stocks and types in “10 protein bars” on the app. He then takes a photo of the specific protein bar he has so that his mom would not get a wrong variant or a different brand. He uploads this photo on the app. He gets a confirmation that his photo was successfully uploaded and that his item on the list has been saved.


Scenario 2


Lilian has just arrived at the supermarket and proceeds to take out her phone to access the “FamilyCart” app. She pulls up this week’s grocery list before heading inside. She gets the first item on the list which is cooking oil and proceeds to tap the box next to it to show a check mark indicating that she has gotten the item. She proceeds to the cereals section to get the cereal her daughter listed down, unfortunately the variant her daughter wanted was not available, so she skipped tapping the item on the list. She heads to the next aisle for what was next on the list and so on. After the checkout she heads back to her car and reviews the list again, she then taps on “end shopping” and drives back home.


IV. The Design Process


A.Sketches


B. User Flow


Dashboard

Onboarding



C. Wire Frames

D. High Fidelity Mock Up





V. Working Prototype


View the working prototype here


VI. Reflection

Working on this project made me realize that having one solution for a problem is not enough. A designer must be able to whip up a number of solutions and also be ready go back to the drawing board if needed.


Improving the design happens as the project progresses. I was reminded constantly that the design process is iterative and I should not be afraid to go in circles to achieve the best solution for my users.


67 views0 comments

Recent Posts

See All

Comments


Commenting has been turned off.
Post: Blog2_Post
bottom of page