APROCOCEM

Challenge

APROCOCEM ran on scattered needs: users with restricted access, a document repository, income and expense tracking, history that had to be queryable, and administrative reports built by hand. Unifying this into an intranet meant keeping document and financial data separate, letting each user see only what corresponds to them, and making reports reflect records exactly — with no intermediate exports.

Approach

I led the full cycle. I started in Figma, defining each module's interface in desktop and mobile versions before writing code. I modeled the MySQL database separating document, financial movement and history entities, and built the API with Node.js and Express: authentication and sessions for access, per-module endpoints, and PDF reports generated straight from those records. On the frontend, Next.js with React Query keeps queries in sync —every write invalidates its cache— and forms validate before reaching the server. Documents are stored in AWS S3 and the application was deployed on AWS with SSL.

Outcome

A private intranet in production that replaces manual workflows: users, documents and finances are managed in one place, history is queryable without spreadsheet exports, and PDF reports come from real data. Since it is a private system, the case explains the work without exposing code or a demo.

Responsibilities

• - Interface design in Figma for every module, in desktop and mobile versions before writing code
• - MySQL database modeling separating users, documents, financial movements and history
• - API with Node.js and Express: user authentication and sessions, per-module endpoints and PDF report generation from the records
• - Next.js frontend with React Query, invalidating the cache after every write and validating forms before reaching the server
• - User document storage in AWS S3
• - Application deployment on AWS with an SSL certificate