---
title: "The hearing aid shipped as software."
date: 2026-09-25
url: https://remiam.co.uk/notes/the-hearing-aid-shipped-as-software
tags: [Hardware, AR, Health]
read_time_minutes: 5
description: "Remiam's read on Meta's Hearing Enhancement feature, announced at Connect on 23 September 2026, and why a medical-grade capability arriving as a paid software mode on general hardware changes how we spec sensors on installations and devices."
---

# The hearing aid shipped as software.

*Published 2026-09-25 · 5 min read · by Liam (Remiam)*

At Connect on 23 September Meta announced an FDA-cleared, over-the-counter hearing aid mode for its glasses: a guided hearing test in the app, amplification tuned to the result, 149 dollars once. The regulated product is the software. The microphones were already there.

Most of what Meta showed at Connect on 23 September was the expected kind of news. A third generation of the Ray-Ban glasses, a camera-free audio pair at 349 dollars, and a 100 gram VR headset with its compute in a puck on your belt, due in spring 2027 at 1,299.99 dollars. The item we keep coming back to was the smallest on stage. Meta called it Hearing Enhancement, and it turns the company's own-brand glasses into an FDA-cleared, over-the-counter hearing aid for adults with mild to moderate hearing loss.

The mechanics are simple. You take a guided hearing test in the app, the glasses tune their amplification to the result, and you switch it on or off by voice. No prescription, set up at home. It costs 149 dollars once after a 30-day trial, or comes with the Meta One subscription, it is eligible for FSA and HSA reimbursement in the US, and it lands on Meta Glasses first, later this year, with the Ray-Ban models to follow.

## The regulated part is the software

Look at what did not change. There is no new hearing aid in the box. The frames already carry an array of microphones, because calls and the assistant needed them, and Meta already ships a Conversation Focus mode that lifts a voice out of a noisy room. What is new is a calibration step, a signal chain tuned per person, and a clearance that covers that combination. The medical device is, for practical purposes, a mode.

That is an unusual shape for a regulated product, and it is the interesting part. The expensive, slow things, the industrial design, the acoustic work, the supply chain, were paid for by a consumer product. The regulated capability rides on top as software, with its own price, its own trial, and its own reimbursement code. Whatever you think of Meta, that is a very efficient way to put a health feature on a lot of faces.

> The hardware decides what is possible. The software decides what you can sell, and when.

## What this means for the things we build

We spec sensors for a living, on kiosks, installations and operational devices, and the habit in most projects is to buy exactly what the first version needs. One microphone because the brief says voice. A camera at the resolution the first feature wants. It keeps the bill of materials down, and it quietly closes the door on the second product, because the second product would have needed a sensor that is not in the enclosure.

Meta's move is the opposite discipline. Put in the sensor the platform could plausibly use, make sure it is good enough, and let later capabilities arrive as software. On a fleet of forty kiosks that is the difference between a new feature being a release and being a refit, which means site visits, engineers, and a quarter of lost momentum. We would rather argue for a better microphone array on day one than explain in year two why accessibility features need new hardware.

- Spec the sensor for the platform, not the first feature. Headroom on audio in particular is cheap at build and expensive to retrofit.
- Make calibration a first-class step. Meta's feature starts with a test and a per-person profile, and so should anything that adapts to the person in front of it.
- Keep regulated or sensitive logic in its own module, with its own switch. If a capability might one day need approval, build it so it can be cleared, priced and turned off on its own.
- Decide how the feature is paid for early. A one-off fee, a subscription, or free forever are different products, and the data model has to know which one it is serving.

## Where we would be careful

A capability you can switch on in software is also one you can switch off, reprice or withdraw in software. For a hearing aid that is not a small thing, and it is a fair question to ask of any platform that sells a health feature as a mode. On our own work the equivalent rule is plain: if a feature is something a person comes to depend on, the licence and the offline behaviour have to be written down before launch, not discovered at renewal.

Still, the direction is clear. General hardware with good sensors, and specific value delivered as software on top of it. It is how phones went, it is now how glasses are going, and it is the right default for most of the physical systems we put into buildings. Buy the ears first. Decide what they are for as you learn.

## References

1. [Engadget, Meta brings FDA-cleared hearing enhancement to its smart glasses (2026)](https://www.engadget.com/2267211/meta-brings-fda-cleared-hearing-enhancement-to-its-smart-glasses/)
2. [The Next Web, Meta unveils $1,299 VR glasses and turns its AI glasses into hearing aids (2026)](https://thenextweb.com/news/meta-vr-glasses-hearing-aid-connect-2026)
3. [Meta, Everything we announced at Meta Connect 2026 (2026)](https://www.meta.com/blog/meta-connect-2026-everything-we-announced/)
4. [Engadget, Everything announced at Meta Connect 2026 (2026)](https://www.engadget.com/2267230/everything-announced-at-meta-connect-2026/)
