Calibry
- Product design
- Platform architecture
- Design system
- Front-end build
Domain rules, queries and formatters live behind a shared router, so a phone client is another consumer rather than a port
The problem
Watch specifications live in forum posts, retailer copy and brand PDFs that disagree with each other, and the reviews sit somewhere else again. The brief was one place that answers three questions at once -- what the reference actually is, what people who own it say, and what it should cost -- and that could grow a phone app later without being rewritten for it.
Our solution
A typed monorepo where the web app owns no logic: domain rules, queries and formatters live in shared packages behind a tRPC router, so an iOS or Android client is another consumer rather than a port. Dark is the identity and the default; light is a designed cool-grey palette rather than an inversion, with its own accent so button text still clears AA. The theme control has three states -- auto, light, dark -- because a two-way toggle throws away the operating system schedule. Every seeded specification is marked unverified until it is sourced, and the catalogue is kept out of the index until it is worth finding.
What it took
Auto, light and dark — auto is deliberate, a two-way toggle throws away an operating system schedule
Every seeded specification is labelled as such, and the catalogue stays out of the index until it is worth finding
The work
Same shape of problem on your side?
Thirty minutes, no deck, and a reply within one working day.
“You will be talking to me, not to an account manager. I scope the work and I am on the build.”