product design · iya 2026
what is troy eats?
USC dining was scattered across USC Card Services, a separate mobile-ordering app, and static dining-hall menu pages - none of which talked to each other. troy eats brings it into one surface: ordering, balance, menus, and community, built around your schedule.
promo video
the problem?
fragmented tools - card balance, ordering, and menus lived in three different places
decision fatigue - too many redundant pages and buttons, no guidance on where to actually eat
no community - no reviews, no photos, no connection between students and chefs
blind wait times - you found out a station was slammed only once you got there
our process?
research - talked to usc students ourselves and catalogued every pain point across the redundant flows
signature feature - an assistant that reads your schedule + location, ranking spots by what's closest, open, and uncrowded
time-aware ordering - tells you exactly when to leave so your food's ready when you arrive
community - students post reviews with photos, chefs reply directly as verified staff
rewards, rebuilt - turned the dead rewards tab into the engine: points for healthy habits, tier status, priority at rush hour
service redesign - meal-swipe transparency, allergen + dietary filters, small nudges toward cheaper, healthier choices
brand - built the full identity: naming, the cardinal-and-gold mark, a tommy-trojan-led campaign
reflection
the final app and pitch deck combined every fragmented tool into one seamless surface. reviewers agreed it was well-made and that the features worked together cohesively.
the biggest open risk is the learning curve - consolidating three tools into one powerful app means new patterns to learn. the next iteration would focus on onboarding and progressive disclosure so the power doesn't overwhelm a first-time user.