Mercado

Creating an effective design system for a food tracking and donation app aimed at reducing consumer level food waste.

User Interface, User Experience
Tools: Figma, Claude, Claude Code, HTML, CSS, JavaScript

The Mercado Scope

Finding common household issues to create a helpful solution to reduce food waste.

People forget what they already have

People don’t know what to do with unwanted food

People need motivation to keep using the app

People forget what they already have

Expiration reminders

People don’t know what to do with unwanted food

People need motivation to keep using the app

Opportunities to Flows

Mercado wireframe user flows: from Home, users add food by scanning a receipt, donate food to a nearby pantry, and redeem points for rewards; the pantry scans the donation QR code, and points are awarded with a receipt.

Adding food

Donating food

Pantry intake

The pantry scans the donor’s QR code.

Points awarded

Redeem points

Creating an Effective Design System

This project was a reinforced the value of an effective, organized design systems when working in a group. Having a single source of truth was vital to creating a cohesive product.

css/styles.css · css/final.css

Color styles

–light-cream#FBF6EA
–cream#EEE5CF
–light-green#C4D99D
–dark-green#354A17
–orange#E05900
–red#AA1D00
–medium-green#607438
–white#FFFFFF

Typography & spacing

–font: “Raleway”, system-ui, -apple-system, “Segoe UI”, sans-serif;

–display700 48px/1 var(–font)
Raleway Hero
–large-title700 32px/1.25 var(–font)
Raleway Headline
–body-strong700 16px/1.5 var(–font)
Raleway Body Strong
–body500 16px/1.5 var(–font)
Raleway Body

Spacing

–spacing-348px –spacing-224px –spacing-112px

Radii

–r-btn14px
–r-card16px
–r-pill27px

Buttons & actions

Button

.m-btn–primary
.m-btn–secondary

Toggle

.m-toggle

Checkbox

.m-checkbox
<button class="m-btn m-btn--primary" type="button">
  Redeem Points
</button>
donorprofile.html

Illustrations & branding

Strawberry mascot waving
strawberry-waving.svg
Pear mascot celebrating
pear-celebrating.svg
Pear mascot looking worried
pear-oops.svg

assets/mascots/

Cards & tiles

Item Card with grippers

Accept
Remove

Brown rice (1)

Expires Mar. 1, 2027
  • .m-item-card__title
  • .m-item-card–grip
  • .m-icon-btn

Drag the card right to accept or left to remove · arrow keys work too

.m-item-card–grip · used on donor_inventory.html

Reward Card

Fortnite V-Bucks: 4,500

  • .m-reward-card__image
  • .m-reward-card__title
  • .m-btn–primary
  • .m-reward-card__points

.m-reward-card

Navigation & bars

.m-nav–user

Forms & inputs

.m-search

Feedback & status

375 pts

.m-pill–points

Integrating Claude, accelerating workflow

To move faster as a team, we brought Claude into our process as a collaborator. We developed screen flows, chose a visual design direction, created wireframes, and started a component library, then used Claude to audit our work, iterate on screens quickly, and code our components in HTML and CSS.

  • Group
  • Claude
  1. 01
    Create screen flows + component library
  2. 02
    Give a report identifying gaps in screen flows and missing components
  3. 03
    Adjust screen flows, add and fix components
  4. 04
    Quick iterations of different screens, connect clickable prototype screens
  5. 05
    Test clickable prototype, make any necessary changes
  6. 06
    Create files, upload to GitHub repository
  7. 07
    Create components in HTML and CSS, create links for components so the group can easily build pages
  8. 08
    Make necessary changes to components, make sure components are coded efficiently
  9. 09
    Build screens looking directly at the Figma file
  10. 10
    Click through prototype, take note of and address any missing components or screens
  11. 11
    Write a report detailing any dead ends the group missed
  12. 12
    Confirm and fix documented issues
  • Group
  • Claude
Group
Claude
GroupCreate screen flows + component library
Run an audit
ClaudeGive a report identifying gaps in screen flows and missing components
GroupAdjust screen flows, add and fix components
Create clickable Figma prototype
ClaudeQuick iterations of different screens, connect clickable prototype screens
GroupTest clickable prototype, make any necessary changes
GroupCreate files, upload to GitHub repository
Create coded version of components
ClaudeCreate components in HTML and CSS, create links for components so the group can easily build pages
GroupMake necessary changes to components, make sure components are coded efficiently
Build screens using components
ClaudeBuild screens looking directly at the Figma file
GroupClick through prototype, take note of and address any missing components or screens
Run an audit for any missing screens or dead ends
ClaudeWrite a report detailing any dead ends the group missed
GroupConfirm and fix documented issues

Each time a change was made, we used Claude to push that update back into Figma, ensuring continuity throughout the entire process.

Up Next

Our next step is bringing Mercado closer to a real product. My team and I are building a working backend with PHP and a MySQL database, so the prototype can store and display real data instead of placeholder content.

I am continuing to test different features of the app on a variety of users, and integrating changes based on issues I find.

↑ Back to Top