The hardware was the easy part

Ask anyone who has shipped a device and you will hear the same confession, usually early: the hardware was the easy part.

Years ago, under the KREK banner, we took Luna Display from concept to contract manufacturer — the electronics and the firmware, across two variants (when USB-C was rare), plus the mechanical design and the introductions that got it built. The software that turned an iPad into a second Mac display was our client’s craft; the firmware that made the device talk to that app was ours. Both sides of that handshake taught the same lesson.

The board came up. The silicon did what the datasheet promised. The circuit design was finished months before the product was.

What consumed those months was everything the schematic does not show.

Where device schedules actually go

Firmware update paths, first. Not the updater that works — the updater that cannot brick a unit when the power blinks mid-flash, on hardware that is already in a customer’s bag in another country. You write the happy path in a week and spend the quarter on the ways it dies.

Then the moving target, which we watched from the firmware side of the fence: a device that talks to a computer inherits every operating system update that computer will ever install. The driver, the transport, the discovery dance — each macOS release renegotiates assumptions you did not know you had made. A device is a promise with a ten-year warranty against an OS with an annual release cycle.

Latency budgets, where the marketing adjective meets a number. “Fast enough” is not a spec. For a display it is a frame; for audio it is a buffer; either way, the returns department is where the rounding errors end up.

And support tooling, the least glamorous line item and the one that decides your margins: the first thousand customers will find configurations you never imagined, and the difference between a five-minute support email and a returned unit is whether the software can see what the device sees.

The pattern holds from the other side

These days I sit mostly on the software side of the same handshake. Fidelia, our audiophile player, lives downstream of everyone else’s hardware — audio interfaces, DACs, dongle-protected plugins — and the same law applies in mirror image. A customer’s interface is not ready when the Mac finishes booting; if the app grabs whatever device exists at launch, it plays his morning playlist through the wrong speakers. His copy-protection dongle wakes up late; if the app gives up on the plugin, his mastering chain is silently missing a limiter. We build for the hardware’s worst morning, because the customer does not file the review under “my interface was slow” — he files it under “your app is broken.”

Software is where a device keeps its promises or breaks them. Teams staff the hardware generously, get a beautiful board through EVT, and then discover the software is most of the product and nearly all of the reviews. Budget it the other way around: the device is the promise. The software is the keeping.

The honest pitch

Audiofile Engineering builds the software that decides whether hardware keeps its promises — the firmware down at the device, and the app up where the customer actually touches it. The products above are the portfolio: a device we took from concept to a contract manufacturer, and an app that survives other people’s hardware every day.

If you are building a connected device and the software side is the part that worries you — it should, and that is the day job. audiofile.engineering/engineering.