Skip to main content
v2026.11,986 entries · CC-BY 4.0

Editorial · CASRAI · AI and ML research outputs

Google adds on-device speech to AI Edge Gallery

Google introduced offline speech recognition and synthesis in AI Edge Gallery on November 10, with reference code for local voice applications.

Published 15 Nov 2026· 3 minute read

Ask CASRAI · free to try

Ask about this story

Ask your first 2 questions free below. Subscribers get 150 a day for $29 a month.

An AI assistant specialized in research administration. It cites the sources behind every answer, labels web answers and says when it can't answer.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

CASRAI is the reference for research administration — bookmark it for the next question.

Google introduced on-device automatic speech recognition (ASR) and text-to-speech (TTS) in AI Edge Gallery on November 10, 2026, alongside reference code for local voice applications. The release combines an Android system-model route through ML Kit with a separate open-weight route through MediaPipe Tasks and LiteRT, according to the Google announcement.

The November 12 Hugging Face article explicitly identifies itself as a republication of the November 10 original. Google described the building blocks as available, rather than announcing a future release date.

The Gallery repository now describes microphone dictation and spoken responses in AI Chat, with selectable speech engines, voices and languages. Its XR Language Teacher combines camera, voice and text input with spoken answers and vocabulary cards. The repository still labels Gallery an experimental beta.

The published reference implementation also demonstrates sentence-level speech playback, including skipping code and tables when reading model responses aloud. This adds a concrete implementation reference for university developers evaluating voice interfaces alongside existing speech-recognition workflows.

Two deployment routes, with different constraints

The implementation choices carry different dependencies. The table combines Google’s release description with its API documentation; a capability in one route should not be assumed to apply to the other.

Route What the sources establish Deployment qualification
ML Kit on Android System speech models managed through AICore and on-device speech services. The speech-recognition API is alpha; Advanced mode supports selected devices.
MediaPipe Tasks Audio Transcriber supports complete clips and streaming audio, with timestamped transcript segments. Interim transcripts can change before final results arrive.
LiteRT model bundles Open-weight speech models package their components in .litertlm files. This is a model-bundle route, distinct from Android-managed system models.

The ML Kit documentation warns that its alpha API has no service-level agreement or deprecation-policy protection and may introduce incompatible changes. It also instructs developers to check model availability and download a model if needed. Its recognition API returns text in the spoken language; translation uses a separate API.

What the release means for research teams

The MediaPipe documentation says Audio Transcriber processes audio locally without sending audio or transcripts off the device. Its browser demo caches model weights after an initial download. Offline inference therefore needs to be distinguished from initial provisioning.

For researchers evaluating interview transcription, the distinction between interim and final text matters when preserving research records. A local voice prototype still needs an explicit choice of transcription conventions and a way to check the resulting transcript against the recording.

Google reports an 8–9% word error rate on FLEURS for its system ASR and about 100 milliseconds before its system TTS starts speaking. These are company-reported measurements, not evidence of accuracy on a particular university’s interview corpus or identical performance across devices.

For research offices, the practical opportunity is to evaluate local processing and inspectable reference code. Our assessment is that processing location alone does not establish participant consent, storage arrangements or access controls for the surrounding application. The announcement supplies implementation options, not an institutional approval for handling research recordings.

Sources

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →