Proptech · One Design System

Reidy: One Design System

One token core behind three products: an internal tool, an iOS app and a web product. Each one grew the system instead of starting a new one.

Role
Design engineer · system, libraries, shipped package
Timeline
Feb 2026 · iOS Aug 3 · Web Dec 4
Platforms
Web + iOS · one core
Package
@reidyai/ds · 0.11.0

3 products on one core: TC, iOS and Web

Foundations first

One core of tokens, set in Feb 2026 before any screen existed. Every product since reads from it.

How the system grew

Three products, one after another. None started a new system: each added a layer to the same core.

TC: designed, then shipped

TC, Reidy's internal tool, came first. Time and budget were too tight: a $20k outsourcing quote, one month. So function came first and styling stayed minimal.

iOS: shipped from the design file

Until launch, the iOS components lived in the app file beside the screens, on the same foundation as TC. Built only as far as launch needed.

After launch: the system takes shape

After launch, the iOS components moved into their own library, with no local variables. Web joined TC's library. Both subscribe to one foundation file.

Same pattern, native shape

The real test is a pattern: the same job, built from each platform's own library, shaped for that platform.

Handoff: everything documented

Documentation is where small teams usually stop. I paired with Claude: it drafted the specs, inventories and parity map from the files, and I decided what each page said and corrected every one.

Deep Adalja · Next case study