Available for selected projects
Frontend developer and cloud architect at AppLoad. I design fast, accessible interfaces and the cloud infrastructure that keeps them reliable.
A selection of products I have designed and built, with my role in each one.
4.8 / 5 on the App StoreFull-stack product
A full-stack product built on Italy’s official fuel prices: an iOS app, a NestJS API and a Nuxt dashboard and web app — from searching the map to managing stations, prices and users.
Two back offices for municipalities and operatorsFrontend ecosystem
Municipality dashboard, operator back office and public website for LeMarche: web interfaces to publish events, places and local content, and to present the ecosystem to users.
+65% mobile conversionsE-commerce platform
A mobile-first online store for sneakers and lifestyle: a dynamic catalogue, a streamlined checkout and infrastructure ready to scale.
From the interface to the infrastructure: I look after the product at every layer of the stack.
Accessible, responsive interfaces, polished in the details and measured on real-world performance.
APIs, data models and integrations designed to stay clear and maintainable over time.
Reliable infrastructure, automated deployments and continuous monitoring of speed and stability.
I’m Federico, a frontend developer and cloud architect. I work where design and engineering meet.
At AppLoad I build web and mobile products and look after the cloud infrastructure behind them. I created and built PitStop, an iOS app for comparing fuel prices, taking care of both its design and development. In my spare time I experiment with new technologies and build personal projects.
Frontend Developer & Cloud Architect
I’m part of the AppLoad team, where we turn ideas and business goals into digital products that are fast, secure and easy to use. I work on both the frontend and the quality of the experience, and on the cloud infrastructure that keeps platforms reliable, secure and ready to scale.
The track playing right now and my most played of the last ten days, updated in real time.
When Spotify is active, this card updates on its own.
Goals, users and constraints, made clear before writing any code.
Architecture and prototypes to validate the riskiest choices early.
Reusable, accessible components covered by tests.
Optimisation, monitoring and iteration on real feedback.
