Case Study Summary
- Problem: Families lose track of inventory and expiry windows in shared fridges.
- Audience: Shared households trying to reduce food waste and duplicate purchases.
- Role: Solo engineer across frontend and API integration.
- Scope: Inventory entry, status tracking, and use-soon prioritization.
- Timeline: App repo created 2024-11-11; backend repo created 2025-05-05; both maintained through 2026.
- Stack: React Native, TypeScript, Node.js API.
- Release surfaces: Mobile app architecture with a separate backend service for content and inventory state.
- Constraints: Fast item input on mobile and low-friction daily maintenance.
- Technical decisions: Typed item states and expiry fields to support predictable filtering and reminders.
- Results: 2-repository architecture (app + API), explicit lifecycle states for active/use-soon/expired items, and an implementation timeline spanning 2024-2026.
- Public metrics note: User/download counts are not published; this page reports only verifiable implementation scope.