Designing a nutrition diary for healthy-minded people to record meals without a hassle.
ReMeal is a meal diary app that uses image recognition to help users write food diaries and ensure nutrition balance.
Targeted users are young adults from age 20-35 who enjoy eating for pleasure, and want to document and understand their meal pattern from their nutrition intake.
Timeline
Mar - May 2023
Role
UX Strategy
Product Design
Storyboard
User Flow
Prototyping
Teammate
Amanda Hamlet:
Root Concept
Wireframing
Deliverables
Product Plan
Storyboard
Prototype
How can we make nutrition balance easier to track and achieve
when calorie counting is painful?
Unlike traditional food tracking apps that focus solely on caloric intake, ReMeal acknowledges that individuals have diverse nutritional needs and diet plans that aligns to their goals.
ReMeal allows users to effortlessly document their meals, gaining insights into their nutrition content without the pressure of calorie counting.
ReMeal help users align with nutrition goal and take pleasure in eating by prioritizing easy data input over calorie counting. Simple visualization helps users understand their nutrition information.
→
→
→
→
→
→
Our audience consists of young adults (approximately 18 - 30 years old) who are interested in health, cooking, and/or nutrition and want to document their meals. More specifically, the characteristics of our target audience ranges from:
Brianna is a nutrition watcher. She mostly cooks for herself to ensure she has balanced food source and nutrition.
She prefers her meal to have lots of vegetables, enough protein, and diverse food sources.
She is always keeping an eye on sodium and sugar of her food because she thinks they're unhealthy.
1
Use camera to capture a meal.
2
View nutrition visualizations and food types
3
View a visualization of their nutrition and the types of foods users are consuming
4
View meal diary to review the food she had for the past few months
→ We then breakdown these goals into more detailed user flow.
Stacked Bubble Chart
uses "size" to compare the nutrition intake amount.
My Friends
See what your friends are having, reply, and like their photos.
Assumption of Data Categorization: We assumed that the current categorization of nutrition data is sufficient without validating its alignment with official guidelines or considering potential improvements.
A lot of quick design decisions are made without a second thought and without validation from users or other perspectives.
Navigation/Information Architecture: Navigation page could examined: Maybe the "Community" page go after the "Goal" page in the navigation bar? Should I use "Analysis" or "Dashboard"? Next time, I would bring in second/third/more opinions as soon as possible to help me recognize terminology or design expressions I took for granted, especially regarding information architecture.
Data Visualization: I would start with understanding how to categorize nutrition data, making it more align with the official guides. I also noticed that a nutrition dashboard would be ultimately complicated over a period of time, and each ingredients provide more than one nutrition, making the data more intertwined. This would create more requirements when designing for this the data visualization.
Information Architecture Review: Take a step back to review the information architecture. Evaluate whether the current structure effectively serves the users' needs and whether any adjustments are necessary based on user feedback or industry standards.
Research Official Guidelines: Dive into official guidelines related to nutrition data categorization. Ensure product aligns with these guidelines to provide accurate and relevant information to users.