06 Case study
Enterprise Component Platform
At QED42, the studio's founder built and maintained production platforms serving 20K to 35K daily active users, and engineered the reusable component library that standardized UI across the company's project portfolio.
- Client
- QED42
- Sector
- Enterprise / design systems
- Year
- 2022 to 2024
- Role
- Full Stack JavaScript Developer
- Engagement
- Full-time
The problem
Every project at the agency was rebuilding the same buttons, forms, and tables, slightly differently. The cost showed up twice: in build time, and in a portfolio of products that did not feel related.
High-traffic endpoints had a second problem: initial load times that punished users on every visit.
The approach
The component library was engineered as a product, not a folder of snippets: 30+ components with consistent APIs, tested with Jest and React Testing Library, and versioned for adoption across teams.
On the platform side, REST and GraphQL APIs over PostgreSQL and MongoDB were optimized endpoint by endpoint, and initial load times dropped 30% through bundle splitting and lazy loading.
React Native iOS work extended the same platforms to mobile, with test coverage held high on critical business logic.
Architecture
A shared component layer above per-project applications, with API and data work done where the traffic actually was.
- 30+ component library
- Consistent APIs
- Jest / RTL coverage
- 15+ adopting projects
- 20K to 35K DAU platforms
- React Native iOS
- REST + GraphQL
- PostgreSQL / MongoDB
- Bundle splitting, lazy loading
The hard parts
Adoption is the hard part
A library nobody uses is a liability with documentation. Adoption across 15+ projects came from consistent APIs, real docs, and treating internal developers as customers.
Performance as a habit
The 30% load-time improvement was not one fix. It was bundle analysis, code splitting, and lazy loading applied as a discipline across high-traffic surfaces.
Outcome
Front-end development effort across the portfolio dropped by 40%, and company-wide UI stopped drifting.
This is the era where the studio's standards were formed: enterprise scale, measured outcomes, and systems that outlive their first project.