Skip to content
LUIGI MICCA

Selected work

The problem, the decisions, the results.

A selection from seven years across e-commerce, enterprise consulting, fashion, industry and open source.

01

Front-end for a global luxury group

Luxury group · via SQLI · 2025–present

The problem

One of the world's largest luxury groups keeps evolving the e-commerce platforms of its maisons: the highest quality bar in retail, brands with different needs, and a shared codebase that has to grow without slowing the release train.

The approach

Front-end engineering as a consultant with SQLI: shared platform components evolved across maisons, performance and accessibility treated as requirements, and quality enforced in review on high-traffic surfaces.

The result

An ongoing collaboration: sturdier shared components reused across the group's brands, with uniform standards on every maison's e-commerce surface.

Read the case study
02

Front-end leadership at callmewine.com

Callmewine · 2024–25

The problem

The online wine shop callmewine.com — 8,000+ labels, a headless Nuxt 3 storefront live in 15+ countries — had a fast-growing codebase: slowing velocity, diverging patterns and a rising count of front-end defects.

The approach

Led the front-end team hands-on as Senior Lead: coding standards and design principles enforced in review, strict TypeScript, incremental refactoring of core components and a shared release checklist.

The result

A faster, calmer team with shared standards in review and more frequent, predictable releases on the storefront.

Read the case study
03

Ticketing for a Mediterranean ferry line

Ferry operator · via adesso.it · 2023–24

The problem

Consulting through adesso.it for one of the Mediterranean's leading ferry operators and other enterprise clients, front-end projects kept starting from a blank page — slow kickoffs, diverging stacks and uneven quality across teams.

The approach

As Frontend Architect: architecture of the ticketing and cabin-booking platform, a reusable walking skeleton, style and quality guidelines, automation and testing scripts adopted across projects.

The result

The ticketing platform shipped on a solid architecture and was then reused as the foundation for new front-end projects with quality gates baked in from the first commit.

Read the case study
04

In-store omnichannel for a fashion brand

Global fashion brand · via Geos · 2021–22

The problem

A customer walks into a store and asks for an item: if the size or colour isn't there, the sale is at risk. Store staff needed a tool showing availability across the whole network.

The approach

A React web app for stores: real-time availability by size and store, item reservation and booking, ship-to-store or home delivery, with payment and fulfilment built into the flow.

The result

Staff close the sale even when local stock is gone, drawing on the whole network's inventory — from the counter, in a few taps.

Read the case study
05

PROCheck: the fleet-inspection app

Prometeon · 2020–21

The problem

The tyre group spun off from Pirelli Industrial needed a mobile app for fleet tyre inspections plus web touchpoints, without doubling the effort per platform.

The approach

One React Native codebase for iOS and Android — the PROCheck app, still in the app stores today — plus React web fronts, sharing design language and logic wherever it paid off.

The result

The app shipped to both stores from a single codebase, at roughly half the effort of two native tracks — and has been in production for over five years.

Read the case study
06

borgo, a self-hosted React framework

Open source · author & maintainer · 2026–

The problem

Teams that want React's developer experience without renting a hosting platform end up gluing together a Node server, a separate API and deploy scripts of their own — and the seams between them are where the bugs and the security holes live.

The approach

Designed and built from scratch: file-based React pages rendered by Bun, API routes in Go with their TypeScript types generated from the Go source, and one Go binary owning the public edge. Every release goes through adversarial bug hunts, mutation testing and a real application rebuilt on top of it.

The result

Published on npm and the Go module proxy under the MIT licence. Rebuilding a real workspace chat app on release 0.30 cut it from 1,510 to 1,433 lines of code while adding features.

Read the case study