LabSavvy

LabSavvy served four different audiences: patients, providers, administrators, and content teams. Each audience had its own independently maintained application. A shared interface change had to be copied into all four codebases, making consistent behavior harder to maintain as the product grew.

The engineering problem was duplication across product boundaries. Fixing one screen did not fix its equivalents elsewhere. The re-architecture needed a shared foundation for common interface and application logic while continuing to support the different experiences each audience used.

I led the re-architecture that brought the four applications onto one shared foundation. Instead of rebuilding the same UI change in four places, the team could implement it once and ship it across the LabSavvy family of apps. This reduced duplicated work and the bugs associated with maintaining separate implementations.

The shared library grew to more than 120 customizable components and 70 reusable hooks. Those components and hooks became a common foundation for the patient, provider, admin, and content experiences. The project stack included React, TypeScript, Mantine, Emotion, and Storybook, with Turborepo and pnpm supporting the shared codebase.

I also extended the product to native iOS and Android. That work carried the patient experience beyond the web while the shared foundation kept the broader family of products consistent. The result was a platform that could evolve across multiple audiences and devices without treating every shared change as four separate pieces of work.