Product and UI/UX design
Screens designed for how people already work. Product interfaces, flows, and design systems with component libraries built for engineering handoff, from people who build products too.
What you receive.
Product interfaces
The screens people use every day, designed around the tasks they come to do.
Flows
The paths through the product, designed around the moment each task matters.
A design system
Tokens, components and patterns: one source of truth for design and code.
Component libraries
Named and structured the way the code will be, so handoff isn't a translation.
Prototypes
Clickable versions to test with real users before anything is built.
Design where the work already happens.
We start from the moment a task matters, not from a screen list. For apprn, that meant designing around the salon chair: the one-time code an artist enters to start a service, and the record it leaves for the owner.
Design and engineering sit in the same team, so a component is designed the way it will be built. What the handoff file says is what ships.
Product and UI/UX design, in practice.
Every piece is labelled by where it comes from: our own ventures, client work published with permission, or a sample.
