Homepage
Discovery, recent meals, invitations, and upcoming events.
USC CSCI 310 · Software Engineering
ShareMeal
A meal, then a reason to gather.
A semester-long full-stack product that turns favorite recipes into shared meals, meals into social events, and dietary information into a safer guest experience.
Product Design · Frontend Engineering · Agile Delivery
FigmaReactSpring BootCucumberJira / Scrum
ShareMeal
discover · plan · gather
MealsEventsProfile
your next gathering
favorite meal
Sunday Dinner
3 recipes · serves 6
Pasta
dinner
Salad
side
Tart
dessert
guest safety
2 dietary preferences matched · 1 allergen warning
04
interfaces owned
02 wk
sprint cycles
01
stakeholder product
~92%
final project score
the product
Four connected moments, not four disconnected features.
The social object wasn’t a recipe. It was the meal people could build and experience together.
01
Recipes
Search an external source and select dishes.
02
Meal
Combine recipes, nutrition, servings, and allergens.
03
Event
Turn a favorite meal into a social invitation.
04
Guests
Match recommendations and surface dietary conflicts.
a product constraint that mattered
The invitation had to protect the guest—not just delight the host.
Allergen data followed recipes into the meal and then into the event. Guests with dietary conflicts were highlighted and warned before accepting an invitation.
event invitation
Sunday Dinner
Vanessaall clear
Guest 02contains tree nuts
Guest 03vegetarian match
my ownership
From visual system to working interface.
I led the evolving Figma mockup and primarily implemented the homepage, login, favorites, and profile experiences on the frontend.
open Figma prototype ↗Login
Validation, error states, and lockout behavior.
Favorites
Save, name, edit, reorder, and activate meals.
Profile
Identity, privacy, and allergen preferences.
how we built it
Ambiguity in. Tested software out.
01
→Probe
Clarify requirements and edge cases.
02
→Design
Make behavior concrete in Figma.
03
→Build
Implement through the Jira backlog.
04
Verify
Test with Cucumber and Spring Boot.
Stakeholder
Requirements evolved through questions and reviews—not from a finished specification.
Accessibility
Labels, semantics, and interaction behavior were part of the build rather than final polish.
Team delivery
Two-week sprints connected Jira, GitHub, implementation, testing, and review.
key takeaway
The hardest part wasn’t drawing the screen. It was turning an ambiguous requirement into something a team could actually build.
ShareMeal taught me to work in the layer between stakeholder intent, product behavior, visual design, engineering constraints, and testable acceptance criteria.
Academic project · private repository · USC CSCI 310