</>
Back
Environmental platforms in productionIn production

Greensoft · EcoREP · 0 Carbono

ReactNext.jsTypeScriptMUIRTK QueryAPIs

Problem

Complying with the EPR law and reporting a carbon footprint means recording, validating and tracing a lot of information (waste per period, documents, states) manually and error-prone.

Context

An internal product for Ambientalia, built at Greensoft (my current job). Two platforms: EcoREP, for waste traceability and EPR-law compliance, and 0 Carbono, to measure the carbon footprint of events.

My role

  • On 0 Carbono I made the design decisions and built the frontend almost solo.
  • On EcoREP I added new views and improved the UI so users got it at first glance.
  • Built a per-period file manager: each uploaded Excel is assigned to its period, so you can review each month's waste traceability.

Solution

  • Multi-layer forms redesigned so users understand them at first glance.
  • State handling driven by what the user uploads: waste pending, ready or approved.
  • File manager that organizes Excels by period and keeps traceability.
  • Frontend in React, Next.js and TypeScript, deployed on Vercel.

Views

Representative mockups · no real data, for confidentiality

EcoREP — waste traceability
EcoREP — waste traceabilityGreensoft · EcoREP · 0 Carbono
Per-period file manager
Per-period file managerGreensoft · EcoREP · 0 Carbono
Waste states
Waste statesGreensoft · EcoREP · 0 Carbono
0 Carbono — event footprint
0 Carbono — event footprintGreensoft · EcoREP · 0 Carbono

Learnings

  • Translating regulatory requirements (EPR law, carbon footprint) into usable interfaces.
  • Designing large forms and state machines that don't confuse the user.

Result

Two platforms in production, used internally by Ambientalia for real EPR-law and carbon-footprint processes.

Back