Sep 2026· Proceedings of the ACM on Interactive Mobile Wearable and Ubiquitous Technologies· 1 citation· 27 references
Speech Recognition and Synthesis
Abstract
Embodied voice assistants offer an intuitive and powerful interaction modality, but they also pose significant privacy-leakage risks when uploading raw voice recordings to the cloud for processing. These voice recordings contain a wealth of private information beyond just spoken content, such as acoustic features that can be used to identify and track users. Existing privacy-protection approaches either rely on encryption and cloud-side processing (leaving raw audio exposed in transit and storage) or use voice obfuscation algorithms whose compute and memory demands exceed what microcontroller-class IoT devices can sustain in real time. As a result, the most resource-constrained microphone-enabled devices, which are also among the most numerous, lack any practical voice privacy protection. We present SafeSpeaker , a lightweight voice obfuscation framework that closes this gap by running entirely on the edge device that captures the audio, breaking the link between user identity and speech before any recording leaves the device. SafeSpeaker uses a time-domain, formant-approximate transformation that avoids the frequency-domain transforms used by prior DSP-based approaches, processing audio nearly 2× faster while matching the identity-obfuscation performance (equal error rate) of state-of-the-art resource-aware methods. We demonstrate the practicality of this design with a real-time prototype on a $3 Arm Cortex-M4 microcontroller that sits between a microphone and an off-the-shelf smart speaker while maintaining the usability to understand and respond to voice commands. By making voice obfuscation feasible at this hardware tier, SafeSpeaker extends on-device voice privacy protections to a substantially larger class of microphone-enabled smart devices.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.