Rethink

Post unwanted items. Pick them up locally. Save money, reduce waste, and cut carbon emissions by keeping reusable goods out of landfills and disposal systems.

Comment

EcoTrade

Problem Statement: Campus communities discard usable clothing while students keep buying new items, increasing waste and avoidable production emissions. EcoTrade reduces that gap by making reuse the easiest option and by showing the impact of each exchange.

Inspiration

EcoTrade was inspired by a simple but widespread problem: perfectly usable clothing is discarded every day, ending up in landfills or requiring energy-intensive disposal. At the same time, people nearby need those exact items. Most sustainability tools emphasize recycling after waste is created; EcoTrade shifts the focus upstream by making reuse the default.

What It Does

EcoTrade is a campus reuse marketplace where students post items, claim them in one tap, and see conservative CO2 savings for every avoided new purchase. The platform enables users to:

  • Discover items available for free nearby.
  • Filter by location and category to find what they need fast.
  • View item details and coordinate pickup after claiming.
  • Participate in reuse without financial barriers.

How We Built It

EcoTrade is a responsive web prototype with a lightweight, modern UI and a simple end-to-end flow. Key technical choices:

  • React + Vite frontend with modular components.
  • Django + Django REST Framework backend for items, claims, and stats.
  • Clear UX states for browse, claim, and post, optimized for demo reliability.

Challenges We Ran Into

  • Balancing simplicity with trust: users need enough detail to feel safe claiming items without clutter.
  • Keeping the solution focused on prevention (reuse) within a tight hackathon timeline.

Accomplishments We’re Proud Of

  • A prototype that prevents waste rather than managing it after disposal.
  • A clean, intuitive interface that feels like a real product.
  • A clear and conservative impact model tied directly to core user actions.

What We Learned

  • Sustainability adoption improves when the action is easy and frictionless.
  • Clear impact signals build trust and motivate reuse.

What’s Next

  • Real-time location filtering and distance-based discovery.
  • Expanded user profiles and posting workflows.
  • Deeper impact tracking (items reused, waste avoided, emissions reduced).
  • Partnerships with campuses and local organizations to scale supply and adoption.

1) Sustainability Impact (25%)

  • Problem relevance: campus clothing waste and avoidable new purchases.
  • Impact mechanism: every claimed item represents one avoided new purchase.
  • Impact methodology: per-category conservative lifecycle estimates (production + transport), intentionally underestimating savings.
  • Metrics shown in-app: total items claimed and estimated CO2 saved, updated after each claim.
  • Assumptions are documented in-app to keep numbers explainable and consistent.

2) Quality of Solution & Innovation (25%)

  • Complete flow: post → discover → claim → coordinate pickup.
  • Strategy: reduce friction on reuse while surfacing transparent impact so users can act quickly and confidently.
  • Innovation: “claim = avoided purchase” links marketplace actions to measurable sustainability impact.

3) Technical Execution (25%)

  • Frontend: React + Vite, optimized for a simple single-page flow.
  • Backend: Django + Django REST Framework with authenticated endpoints for items and claims.
  • Core endpoints: auth (signup/login/logout), items (list/create/update/delete), claim action, and stats.
  • UX details: default filters, one-tap claim, inline validation, and messaging on success/error.

4) Feasibility & Scalable Design (15%)

  • Rollout plan: pilot with one campus → expand regionally → multi-campus network.
  • Adoption strategy: partner with campus sustainability offices and reuse clubs; seed listings at launch.
  • Expansion: add verified org partners (thrift stores, donation drives) and regional hubs for more supply.

5) Presentation & Demo (10%)

  • Demo goal: show a flawless “happy path” with no bugs during the demo.
  • Demo script (60–90s): login → browse → claim → see impact update → post an item.
  • README begins with a concise problem statement as required by the rubric.
  • GitHub Pages bonus: build the frontend and deploy output to docs/ to enable Pages.

Getting Started

Frontend

cd frontend
npm install
npm run dev

Backend

cd backend
python manage.py runserver

Set VITE_API_BASE_URL if your API runs on a non-default URL.

Built With

Share this project:

Updates