Skip to content
</>
Back
Interfaces for environmental operationsProduction

Professional project

GreenSoft · EcoREP · 0 Carbono

  • React
  • Next.js
  • TypeScript
  • MUI
  • RTK Query
  • REST APIs

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.

Objective

Turn environmental and regulatory processes into clear modules for recording, reviewing and processing operational information.

My role

  • On 0 Carbono I implemented the whole frontend. I used HuellaChile's frontend as a reference for structure and experience.
  • On EcoREP I took part in frontend work on specific modules of a shared platform.
  • On the EcoREP dashboard I implemented multi-select filters: charts and tables are generated from what the user selects.
  • Built a per-period file manager: each uploaded Excel is assigned to its period, so you can review each month's waste traceability.

Architecture & decisions

  • A modular frontend with React, Next.js and TypeScript, Material UI components and server state through Redux Toolkit/RTK Query.
  • Modules consume REST APIs and separate forms, filters, visualization and file management.
  • 0 Carbono runs on Next.js 16 and React 19 with a feature-first structure; EcoREP is an older codebase, on Next.js 13.

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 modules in React, Next.js and TypeScript integrated with APIs and the team's deployment flow.

Challenges & trade-offs

  • Representing states and regulatory requirements without passing process complexity straight to the user.
  • Evolving modules inside shared platforms while staying consistent with the team's work.

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.