ROLE:
PROJECT MANAGER & UX DESIGNER
TOOLS:
FIGMA, FIGJAM
TIMELINE:
12 WEEKS
PROJECT TYPE:
MOBILE APP DESIGN
Ample
about.
problem.
Food waste is a major issue in the U.S., with restaurants discarding surplus food that could still generate profit. Meanwhile, college students struggle to find affordable, convenient meals.
How might we connect these restaurants to students who would want to purchase their surplus food at an affordable rate?
Ample bridges this gap by connecting students with local restaurants, allowing them to purchase excess food at a reduced price. Through the app, students can browse participating restaurants, view available meal boxes, and place orders for pickup.
research.
ideation.
After reviewing our research, each team member sketched key design elements for Ample, drawing from our How Might We statements and user personas. We iterated, critiqued, and voted on our favorite ideas using star stickers to finalize core features:
Onboarding carousel to introduce the app’s purpose in reducing food waste.
Dietary restrictions page for user customization.
Confirmation screen summarizing orders with a QR code.
Next, we mapped a user flow to connect our top ideas, identifying gaps and adding necessary screens.
prototyping.
We used our user flow map to guide the design, starting with low-fidelity wireframes in Figma based on our sketches. Once refined, we developed high-fidelity wireframes, incorporating our brand identity from the style guide.
To reflect Ample’s eco-friendly mission and cost-saving focus, we chose green as the primary color and selected typography inspired by our research on similar apps.
testing.
We conducted 11 user testing interviews with both frequent and infrequent food app users to identify issues and opportunities. Testers freely navigated our prototype while answering task-related questions.
Key findings:
Missing features: Some dietary options (e.g., vegetarian) were unavailable, and certain pages were hard to access.
Design inconsistencies: Graphics varied across pages, and screen transitions lacked uniformity.
Lack of clarity: Users didn’t realize the app was for pickup only, and some FAQs were unclear.
We prioritized insights by importance and frequency, then refined our mid-fidelity prototype accordingly.
result.
Personalized Home Page
Users receive tailored recommendations based on preferences, location, and filters like price range and radius for efficient browsing.
Detailed Restaurant Pages
Each restaurant listing includes pickup time slots, possible box contents, and cuisine images, making ordering seamless.
Active Order & QR Code
After purchase, users get a summary with pickup details, the restaurant’s address, and a QR code for easy order retrieval.
what's next.
The next step for Ample is to develop the vendor side of the app. This involves:
Vendor Onboarding – Streamlining sign-up and account verification.
Menu Management – Enabling vendors to update surplus food inventory.
Order Management – Providing tools to track and manage orders.
Analytics & Reporting – Offering insights on sales and waste reduction.
Communication Channels – Allowing vendors to connect with users directly.
