Two-Sided Waste-Management Mobile App

I. System Context & Constraints

Technical reality: Commercial establishments — hotels, restaurants, residential complexes, offices — coordinated waste collection ad hoc, with no schedule, no record, and no visibility into when a pickup would actually arrive. The opportunity was a two-sided platform connecting waste generators with collection providers, but a two-sided build is also two products at once.

Director’s constraints: A cross-platform mobile build on a fixed timeline, a brand-new product with no existing data to lean on, and a feature surface (scheduling, live tracking, history, profiles) wide enough that shipping everything at once would have sunk the launch.

II. Critical Path & Architectural Choices

The defining decision was scope sequencing, not a framework choice. I scoped phase one to the generator side only — the demand side that proves the product — deferring the provider console until the core loop was validated. That kept the first release shippable while still standing up the full schedule → pickup → history loop a paying customer would feel.

The app was built in Flutter for a single cross-platform codebase, on Firebase for authentication, real-time data, and storage — a managed backend that let a lean team move without operating infrastructure. Live truck tracking and calendar-based scheduling were the features that turned an opaque, call-around process into a transparent, plannable one.

III. Governance, Risk & Team Topology

I directed design, engineering, and QA through a phased plan: authentication and the dashboard, calendar and scheduling, the pickup-request flow, history logging, and live tracking — each a checkpoint rather than a big-bang release. Design ran in Figma ahead of build so engineering worked against settled flows.

The principal risk was scope on a new two-sided product. Cutting phase one to the generator side was the governance lever that contained it: a coherent, demoable product on time, with the provider side and deeper analytics staged as fast-follows once the core was proven in users’ hands.

IV. Quantifiable Outcomes