Amid
All work
03FemTech

ScreenMe

A UK-based healthcare platform providing at-home microbiome testing and consultation services. I built the consultation booking flow and structured the codebase as a monorepo with shared packages and a consistent design system.

Organization Freelance · Production Product

Role Frontend Developer

screenme.co.uk (opens in a new tab)
Production healthcare product
LiveProduction healthcare product
Shared packages and design system
MonorepoShared packages and design system
Responsive booking experience
AccessibleResponsive booking experience

01

Overview

ScreenMe is a UK-based healthcare platform offering at-home microbiome testing and consultation services. It is a live product with real customers, delivered as freelance work.

My contribution centred on the consultation booking flow and on the structure of the codebase itself.

02

The Problem

Booking a consultation is the point where a healthcare product either earns trust or loses it. The flow has to be clear, responsive on the devices customers actually use, and accessible.

Behind it, the codebase had to support shared UI across the product without each surface re-implementing the same components in a slightly different way.

03

My Approach

Build the booking flow as a first-class product surface — responsive and accessible from the start, not retrofitted — and put the reusable parts where every surface can reach them.

Structuring the repository as a monorepo made the design system a shared package rather than a convention people are asked to remember.

04

Architecture & Technical Decisions

apps/

Application
Additional surfaces

packages/

Design system
Shared packages

Dependencies point one way. Applications consume shared packages; shared packages never import an application.

Applications consume shared packages; the design system is a dependency, not a copy-paste convention.
  • Next.js for the application layer.
  • Material UI as the component foundation, extended by a consistent design system.
  • Monorepo structure with shared packages, so design-system changes propagate instead of being duplicated.
  • Responsive and accessible interfaces throughout the booking flow.

05

My Contribution

  • Built the consultation booking flow.
  • Developed responsive and accessible interfaces.
  • Structured the codebase as a monorepo.
  • Supported shared packages and a consistent design system.
  • Delivered functionality for a live healthcare product serving real customers.

06

Outcome

A production-ready user experience for a live healthcare product, on a codebase organised so shared UI stays consistent as the product grows.

07

Technology

  • Next.js
  • Material UI
  • Monorepo
  • Design Systems