What AI services can run on audio hardware?
- Hearing personalisation — the device adapts output to the individual ear.
- Adaptive sound — EQ, ANC, and transparency that respond to environment and content.
- Voice intelligence — on-device commands, assistants, and conversational interfaces.
- Translation and transcription — live language features, usually hybrid on-device/cloud.
- Health and context signals — in-ear sensing where hardware supports it.
Should AI run on-device or in the cloud?
On-device wins on latency, privacy, offline function, and per-user cost at scale. Cloud wins on model size and update speed. Audio features that touch the listening experience — personalisation, adaptive sound, wake words — need on-device execution; a round trip to a server is audible. Most production systems are hybrid: on-device for the real-time path, cloud for heavy inference.Should you build or licence?
Building in-house means hiring DSP engineers, ML engineers, and embedded developers who know the specific SoC — a team most brands can’t assemble or retain. Licensing means integrating an existing AI software stack already ported to your chip platform. The build route makes sense if audio AI is your core business. For everyone else, it’s cost without moat. [whitepaper: integration cost comparison]What drives integration cost?
- SoC compatibility — software already ported to your chip is cheap to adopt; porting from scratch is not.
- Where the AI runs — firmware-level integration costs more upfront than app-level, but doesn’t depend on the user installing anything.
- Feature scope — one feature or a platform. Platforms amortise better across a product line.
- Update infrastructure — OTA capability determines whether the product improves after it ships.