Campus Food Ordering System

A student-powered food delivery app that lets solo diners join live group orders with other students nearby, splitting the delivery fees so you never have to overpay for a single meal again.

College students often face the frustrating dilemma when it comes to food delivery: either place a large enough order to offset the high delivery fee, or pay a steep price for a small, single meal. Whether the restaurant is five miles away or just one, the delivery fees often remain the same.

Difficult product traceability

Buyers lack trust in product quality, while it's hard for farmers to prove the quality

Farmers' problem

Lack of online trade

Low profit margins

Solution (demo) 📱

Solo diners can join group orders with other students nearby.

Students can join or host the live group orders with other students (whom they don't know). This helps split the cost between solo diners flexibly
All orders have transparent delivery pricing, so students know if they’re overpaying for a short-distance delivery

Let's backtrack the process ⚙️

📍 Mapping Pain Points

As we walk through the insights, we see the common pain points among the student users:

Harvest under pressure 🕐

“I don't know exactly how much I’ll harvest, but I still have to commit to a number, it's always a gamble."

Price controlled by middlemen 💰

“A good harvest should be good news, but it often means selling cheaper just to avoid waste."

Lack of credibility 📦

“I worked hard for that crop, but once it leaves my farm, I don’t know where it goes or how it’s sold."

🔎 Competitor Analysis

To understand the market, we analyzed existing food delivery platform (UberEats, EASI, DoorDash) to know more about the current experience of users.

Here, we evaluate the strengths, weakness, UX design and business models.

Key findings 🔑

Most apps are optimized for general users, overseeing the students needs.
While 'group order' features exist, they typically assume social connections.
Users may find it difficult to understand how total costs are calculated.

🧩 How Might We…?

To move from insights to solutions, we turned each major pain point into an opportunity for solutions:

How might we make the process easy for farmers to manage their sales independently?

How might we improve farmers product distributions to buyers without barrier in trust?

✏️ Design Iterations

I tested my design solution with the same users I interviewed with and their feedbacks allow more insights that gives valuable design iterations.

⚠️ DESIGN ITERATION #1

What I Tried?

A simple view list of nearby group orders that is sorted by the countdown timers until the order is closed.

What Went Wrong?

This helped with quick scan, however…

Not every user knows the location of the pick-up point. Users need to go to map app to search for a specific location which is overwhelming if there are multiple orders.
Users prefer to sort orders in distance rather than time windows.

⚠️ DESIGN ITERATION #2

What I changed?

Added an in app map and pick up distance from user's current location.

Added the filter or sorting options (distance, time window, cost) that with the minimum number

Why it worked?

Users can scan quickly based on preferences and easily know the pick up location without the need to navigate to other apps, minimizing the process of searching.

🟨 Affinity Diagraming

To validate the ideas, I conducted user research with 16 students within my school campus to understand their needs, behaviors, and motivations.

After collecting all the data through the interviews with the target users, I sort them into groups of similar items to synthesize the key patterns, user needs, and pain points.

Average hours to code 1 screen's UI