Interfaces for software people use with their ears.
Audio interfaces have a problem that ordinary product design does not: the thing being controlled is invisible, continuous, and judged by ear. A control that looks correct and reads wrong under the hand is a failure regardless of how it renders.
We design plugin panels, desktop applications, and the web pages around them, then build the front end so the design survives contact with the code.
Layout, control behaviour, metering, and state. Sensible resizing, keyboard and mouse behaviour that matches what engineers expect, and rendering that stays smooth while the audio thread is busy.
Knob laws, detents, modifier behaviour, and metering ballistics are the part users describe as quality. We set them by ear, against reference hardware or plugins where a reference exists.
Product pages, documentation, and account or download flows. Built responsive, with the type and spacing decided once and applied everywhere.
Contrast, hit targets, text size, and behaviour at high DPI and on small screens. Foldables and tablets included where the product runs there.
Yes. If there is a design system we extend it. If there is not, we build a small one rather than styling screens individually.
Either. Most clients take the implemented front end, because the gap between a design file and a running panel is where quality usually leaks out.
JUCE, or a web view where the interface benefits from it. We will tell you which one fits before starting.