Varada P
UX/UI Designer
No-code Developer
Freelancer
Brand Designer
Dog Lover
EatYaar
Share More. Waste Less.
Project Summary
EatYaar is a community-driven food sharing platform designed to connect people with surplus food to those who need it quickly, locally, and effortlessly. The goal is simple: reduce food waste while making access to meals easier within communities.
Background
The everyday waste no one talks about
Walk into any home after a gathering, any kitchen after a busy weekend, and you'll find the same thing containers of food that nobody will finish, quietly moving toward the bin. This isn't a crisis that makes headlines. It happens quietly, millions of times a day, in homes across every city and town.
India alone wastes an estimated 68.7 million tonnes of food annually. Much of it comes not from commercial supply chains, but from households — events, family meals, celebrations where food was prepared generously and couldn't all be consumed. At the same time, food insecurity remains a daily reality for a significant portion of the same communities where that food is being thrown away.
The gap isn't supply. It's connection. The food exists. The need exists. What's missing is the bridge between them fast enough, simple enough, and trustworthy enough to use in the moment.
Why Current Solutions Fall Short
Existing solutions donation drives, food banks, community kitchens do important work. But they operate on schedules. They require planning, transport, and coordination. They can't handle the spontaneity of a Tuesday night when you've cooked too much dal and your neighbor's family hasn't had a proper meal.
EatYaar was built for that Tuesday night. For the working professional who cooked for ten and is eating alone. For the student who baked too much and doesn't want it to go to waste. For the retired couple who made biryani for a function that got cancelled.
The insight at the core of EatYaar is simple: willingness to share already exists. The bottleneck is convenience. If sharing food were as easy as posting a story, people would do it constantly.
Understanding the Problem
What people actually experience
Before designing anything, I mapped out what the sharing and receiving experience actually felt like from the user's perspective not in ideal conditions, but in the real moments when the problem occurs.
Donors have a short window. Food is fresh now, but not for long. They’re often busy and won’t spend time on complex steps. If sharing takes more than a minute, they give up.
Recipients face the same urgency. Food gets claimed quickly. If discovery is slow or the process feels unclear, the opportunity is lost. There’s also a need for trust and comfort when requesting from strangers.
"I had leftover food from a birthday party — enough to feed five people. I just wanted someone nearby to take it. I didn't know who to call or where to post."
"I found an app once that was supposed to do this, but I had to register and verify and wait. By the time I figured it out, I'd already thrown the food away."
"I'd definitely use something like this if it was as simple as posting on Instagram. But most apps make it feel like a whole process."
These weren't edge cases. They were the norm. The core problem crystallized into a single design constraint: every second of friction is food that gets wasted instead of shared.
Competitive Landscape
To understand the gap EatYaar fills, I studied four platforms in the food-sharing and food-waste space: OLIO, Too Good To Go, Plenti, and NoWaste.
OLIO A community-driven app where individuals share surplus food for free. The model is right but the posting flow has too many steps for a spontaneous act. One extra screen is enough to kill the impulse.
Strengths: Free, community-driven, real-time listings, global reach. Limitations: Multi-step flow, interface complexity, not optimised for speed.
Too Good To Go Connects consumers with restaurants selling unsold food at a discount. Clean, structured, commercially proven but it's a marketplace, not a community. Individual households are entirely outside its model.
Strengths: Strong business integration, structured UX, proven revenue model. Limitations: Not for individuals, food isn't free, no peer-to-peer sharing.
Plenti (Kerala-based, currently in Trivandrum) India's first surplus food marketplace. Restaurants and supermarkets list discounted surplus as "Surprise Drops" users browse, reserve, pay, and pick up. It has real local traction, especially among students, and a clean no-delivery-fee model. As a Kerala-native app, it's the most geographically relevant competitor to EatYaar.
Strengths: Kerala-native, simple UX, local traction, no delivery fees, helps businesses monetise waste. Limitations: B2C only, no individual donors, food isn't free.
NoWaste focuses on personal food inventory management — tracking expiry dates to prevent waste at home. It's a prevention tool, not a sharing tool. It solves a different problem. The gap across all three is the same: none of them are built for the speed and simplicity that individual, spontaneous sharing requires. EatYaar was designed to live precisely in that gap.
User Persona
Anaswara, 25 — Working Professional, Kozhikode
After a weekend family gathering, Anaswara has more food than her household can finish. It's fresh, it's good, and it's heading for the bin — not because she doesn't care, but because she has no easy way to share it.
She wants to act now, not coordinate a donation. She wants it gone in less time than it takes to pack it up.
"I don't want to waste food. I just need an easy way to share it."
Anaswara isn't unusual. She's the majority of EatYaar's donor base — willing, time-constrained, and one inconvenient screen away from giving up.
Empathy Map
After a weekend family gathering, Anaswara has more food than her household can finish. It's fresh, it's good, and it's heading for the bin — not because she doesn't care, but because she has no easy way to share it.
She wants to act now, not coordinate a donation. She wants it gone in less time than it takes to pack it up.
"I don't want to waste food. I just need an easy way to share it."
Anaswara isn't unusual. She's the majority of EatYaar's donor base — willing, time-constrained, and one inconvenient screen away from giving up.
Strategy
Design for the distracted, generous person
People in a moment of surplus aren't focused — they're mid-cleanup, time-pressured, and one extra tap away from giving up. Every design decision was made with that person in mind.
Speed over completeness. Post food in under 90 seconds — photo, name, quantity, pickup window. Nothing more required.
Images over text. A real photo communicates everything instantly and builds the trust that gets requests sent.
Proximity first. The feed is distance-sorted by default. The most relevant food is always at the top, no setup needed.
One-tap requesting. Recipients request from the feed card in a single tap. The system connects; people handle the handoff.
Designing for dignity
Donors shouldn't feel like they're discarding food. Recipients shouldn't feel like they're asking for charity. Every interaction is framed as a community exchange — not a donation.
Listings use everyday language: "fresh roti from tonight's dinner" not "surplus food item." The request button says "I'd like this" not "Claim." Small words, real difference.
Trust by design, not by feature
Profiles show a first name, neighbourhood, and a count of shares and received meals — not a star rating, which feels punitive, but a quiet record of community participation. Reliability reveals itself over time.
Design Process
Understand → Define → Ideate → Design → Test
Visual Design
Primary — #FE5B00 A warm, energetic orange that anchors the brand. Used for key UI elements, headers, and active states. It signals action and warmth without aggression.
CTA / Buttons — #FE5B00 → #C04806 Buttons use a linear gradient from the primary orange to a deeper burnt orange. The gradient adds depth and makes interactive elements feel tactile and inviting — clearly tappable, never flat.
Success — Green Used for confirmation states — successful posts, completed handoffs, received meals. Green communicates that something good just happened, reinforcing the positive loop of sharing.
Background / Text — Light neutrals and dark greys Keep the interface clean and let the food photography do the visual heavy lifting.
Why Orange:
Orange sits at the intersection of warmth and urgency — exactly the two emotions EatYaar needs to trigger. Warm enough to feel like a neighbour handing you food. Urgent enough to communicate that availability is time-sensitive. It also photographs well against food imagery, making the UI feel alive rather than sterile.
Typography
Poppins — chosen for its rounded, friendly geometry that matches the community tone of EatYaar. Clean and highly legible at small sizes, which matters on a feed-heavy mobile interface.
Design Language:
Warm without being loud. The orange anchors the brand and drives every CTA. The gradient adds energy to buttons without needing extra decoration. Green confirms positive moments — a request accepted, a share completed — so users always know when something good just happened.
High-Fi Screens
Impact
The design targets the root cause of food waste at the individual level — not awareness, but friction. When sharing is as easy as posting a story, people do it.
The first successful share is the hardest. Once a user completes a full loop — posts food, gets a request, arranges a pickup — they are significantly more likely to do it again. The experience is designed to make that first loop feel effortless and rewarding.
Learnings
The willingness to act is already there — remove the barriers, don't build new ones. Almost every design decision on EatYaar came back to this. Users want to share. The job of the interface is to not get in the way.
Speed is a feature, not a shortcut. Designing for 90-second posting wasn't about cutting corners — it was about respecting the actual context in which people use the app. A flow that works in the real moment of spontaneous generosity is more valuable than a comprehensive one that nobody completes.
Trust is built through consistency, not claims. Calling an app "safe" or "community-driven" doesn't make users feel safe. Showing them real names, real neighbourhoods, real photos, and a visible record of community activity does.
Language is interface. The words on a button — "I'd like this" versus "Claim" — change how the interaction feels. In a space with inherent social dynamics, tone is a design decision.
Dignity is a UX requirement. For any platform that involves need and generosity, the design must ensure that both sides of the exchange feel like participants, not roles. The moment an interaction feels transactional or charitable, the emotional contract breaks.