The future of smart glasses is missing a key audio component - and I tried it already
Briefly

The future of smart glasses is missing a key audio component - and I tried it already
"A dynamic driver consists of a magnet, a voice coil, and a diaphragm, and it uses electrical signals to generate magnetic fields that move the diaphragm and coil, creating sound. Dynamic drivers are cost-effective, power-efficient, and leverage air displacement to reproduce the prominent bass response most consumers enjoy. The downside to dynamic drivers is that they take up space and weight within your headphones and earbuds, and can often distort sounds at high volumes, struggling to maintain clarity."
"Consumer technology continues to advance every year. Smartphones debut with on-device, AI-powered features, smart glasses project displays of your daily tasks, and smartwatches can help you treat a cold before you feel its wrath. However, dynamic drivers, which are inside all of these products, have remained largely unchanged over the last 100 years. Also: CES 2026: Biggest news on TVs, smart glasses, robots, and more Dynamic drivers are the small transducers found inside earbuds, headphones, smartphones, smartwatches, and smart glasses, which utilize fundamental laws of physics to deliver sound to your ears. Yet, as your devices become smarter and more powerful, tech providers like xMEMS believe that your audio experiences should be equally innovative."
xMEMS produces tiny MEMS audio and cooling chips designed to replace century-old dynamic drivers in earbuds, headphones, smartphones, smartwatches, and smart glasses. Dynamic drivers rely on magnets, voice coils, and diaphragms to move air and produce bass, but they add bulk, weight, and can distort at high volumes. xMEMS’ MEMS chips aim to reduce size and weight, improve thermal management, and maintain sound clarity while enabling new design possibilities in consumer devices. The technology shows promise, but manufacturer adoption and broad implementation remain a work in progress.
Read at ZDNET
Unable to calculate read time
[
|
]