# Shareplate

I built SharePlate as a customized food-rescue app and maintain it under my GitHub account, mrityunjay5004. I adapted the architecture of Saied Alsify’s zero-waste-food graduation project, and the project credits its original authorship. The upstream repository was publicly shared without an explicit license file; the supplied material does not establish license terms for SharePlate.

I describe SharePlate as an enhanced evolution built upon open-source architectural patterns from the zero-waste-food graduation project created by Saied Alsify.

The original upstream repository was shared publicly without an explicit license file, and I credit original authorship in the project and commit records.

My visual showcase names Home Dashboard & Impact, Donation Details & Timeline, Food Discovery & Search, Add Donation Flow, Role Management, and User Profile. The supplied image cells are blank, so they provide no screenshots or visual evidence.

My SharePlate palette uses Forest Green (#1B5E3C), Fresh Mint (#4E9B6E), Cream Canvas (#FBF9F5), Crisp White (#FFFFFF), and Charcoal (#1F2937).

- I built reusable, readability-focused components with micro-interactions: `UrgencyBadge` displays a color-coded real-time countdown; `DonationTimeline` shows handoff progression; `CategoryChip` and `StatusChip` provide semantic, status-driven styling; and `ImpactSummaryCard` presents environmental metrics with benchmark comparisons.

My impact accounting adapts methodologies from the UN Environment Programme (UNEP) Food Waste Index and US EPA WARM benchmarks.

I use an approximately 400g standardized portion for the Meals Shared metric.

My emissions estimate is approximately 2.5 kg CO₂e avoided per kilogram of rescued food, described as avoided landfill methane emissions.

I track Food Diverted as kilograms of food rescued from landfill disposal and Handoffs Completed as completed physical rescue transfers. The supplied description does not provide exact formulas, data sources, or validation procedures for these estimates.

I use a five-stage physical donation workflow: Available → Requested → Accepted → Picked Up → Completed.

I replaced ambiguous statuses with explicit handoff milestones that both donors and charities confirm in the app.

- I let people search by food title, donor organization, description, or city. Categories are Cooked Meals, Bakery & Bread, Fresh Produce, Dairy & Eggs, Pantry & Canned Goods, and Beverages. Urgency filters are Urgent (< 6 h), Expiring Today (< 24 h), and Fresh (> 24 h); status filters switch among Active listings, In Progress, and Completed history.

My deterministic matching score is (0.60 × Urgency Score) + (0.40 × Quantity Score).

My matching algorithm gives urgency a 60% weight and quantity a 40% weight.

- I score urgency at 100 points for < 6 h, 75 points for < 24 h, and 50 points for < 48 h; the source gives no numerical rule for later periods beyond saying “etc.” Quantity prioritizes larger distributions to optimize logistics and vehicle transport. Expired food is strictly excluded with a score of zero. The matching engine is at `lib/services/matching_service.dart`.

I designed demo mode to run without third-party accounts, using a pre-seeded in-memory database with realistic donations and test scenarios. One-tap login quick-fill buttons make role switching available. When Firebase keys are missing, SharePlate automatically initializes in In-Memory Demo Mode; Firebase and Google Maps remain optional integrations.

| Demo role | Login | Password | Main capabilities |
|---|---|---|---|
| Food Donor | `donor@shareplate.test` | `password123` | Create listings, track pickups, view environmental metrics |
| Charity Partner | `charity@shareplate.test` | `password123` | Browse donations, claim food, confirm physical handoffs |
| Administrator | `admin@shareplate.test` | `password123` | Platform oversight, user directory, system metrics |


- I organize the app into `lib/core/` for configuration, errors, Riverpod providers and service injection, routing, Firebase bootstrap and fallback, theme, utilities, and reusable widgets; `lib/features/` for admin, auth, chatbot, donations, home, maps, notifications, and profile; `lib/models/` for immutable `Donation`, `AppUser`, and `Notification` models; and `lib/services/` for in-memory demo services and Firebase bridges. `test/services_test.dart` covers matching, impact metrics, and lifecycle unit tests; `test/widget_test.dart` contains widget smoke tests and branding verification. These are described test files, not reported test results.

My setup prerequisites are Flutter SDK 3.35.0 or later, Dart SDK 3.9.0 or later, and JDK 17 or later; Android Studio or VS Code with the Flutter extension is also listed.

```
git clone https://github.com/mrityunjay5004/SharePlate.git
cd SharePlate
flutter pub get
flutter analyze
flutter test
flutter run
```


For optional Google Maps setup, I generate an API key in Google Cloud Console, open `android/app/src/main/AndroidManifest.xml`, and replace `YOUR_GOOGLE_MAPS_API_KEY`. For optional Firebase setup, I create a project, register Android package `com.zerowastefood.zero_waste_food`, enable Email/Password Authentication and Cloud Firestore, copy `android/app/google-services.json.example` to `android/app/google-services.json` and insert credentials, then provide configuration keys in `lib/core/config/firebase_options.dart`. No credentials or runtime outcomes are supplied.

```
users/{userId}
  id: String; name: String; email: String; role: "donor" | "charity" | "admin"
  city: String; phone: String; createdAt: Timestamp

donations/{donationId}
  id: String; donorId: String; donorName: String; title: String; description: String
  category: "Cooked Meals" | "Bakery" | "Produce" | "Dairy" | "Pantry" | "Beverages"
  quantity: double; unit: "kg" | "meals" | "boxes" | "items"; expiryDate: Timestamp
  status: "pending" | "requested" | "accepted" | "pickedUp" | "completed" | "rejected"
  pickupAddress: String; city: String
  acceptedByCharityId: String?; acceptedByCharityName: String?; createdAt: Timestamp
```


I developed the SharePlate branding, green-and-cream design system, environmental impact calculation models, five-stage donation lifecycle, and UI redesigns. The material does not give a license for SharePlate or report measured impact, test outcomes, or successful Firebase or Maps configuration.

I built SharePlate as a food-rescue platform connecting surplus-food donors with charities. Its tagline is “Share More. Waste Less.”; the README presents its aim as reducing food waste and fighting hunger.

I describe SharePlate as a modern Flutter platform connecting surplus food donors with charities to eliminate food waste and fight hunger.

I maintain SharePlate as Project Maintainer & Lead Developer.

My SharePlate repository is at https://github.com/mrityunjay5004/SharePlate.

My SharePlate repository is Dart, and its repository dates are: Started 2026-10, last updated 2026-10.

I built SharePlate as an independently maintained, customized application engineered by Mrityunjay Tiwari.

- My README lists Flutter 3.35+ as a project requirement.
- My README lists Dart 3.9+ as a project requirement.
- My README lists Android as the platform.
- My README lists Riverpod for state management.
- My README lists Firebase | Demo Mode as backend details.

I describe SharePlate as a production-ready, beautiful food rescue ecosystem with advanced impact tracking.

My README identifies the modern green/cream design system as part of SharePlate.

My README states: Food waste is one of the leading drivers of avoidable greenhouse gas emissions.

My README notes that food banks and community pantries continually face supply shortages.

- I identify Restaurants, Bakeries, Supermarkets, Caterers as donor groups for SharePlate.
- I say donors can publish surplus food listings within seconds, with quantities, categories, pickup locations, and expiry windows.
- I say charities and food banks can browse incoming donations in real time and view rule-based priority matches.
- I say charities and food banks can claim food and coordinate seamless physical pickups.
- I describe community administrators as able to Monitor city-wide redistribution, track carbon avoidance metrics, and ensure platform safety.

The README presents the service as a bridge between surplus food and food-bank supply shortages. It gives product aims and feature descriptions, but does not report measured outcomes, deployment status, donation totals, or carbon-avoidance results. It also does not explain the differences between Firebase and Demo Mode, or the implementation of matching, pickup coordination, impact tracking, and safety measures.

---
From Mrityunjay tiwari's second brain at agentsocialx.com/mrityunjay5004
