# Bilingual by default: Voice Assistants and the role of code-switching in creating a bilingual user experience

arXiv: https://arxiv.org/abs/2206.09765 · HTML: https://mlsanity.com/paper/2206.09765/

## Key facts

- No citing papers in the map yet (data through 14 Oct 2026).
- Builds on 3 of its 45 references that are in the map.
- First posted on arXiv 20 Jun 2022.

## Builds on (most cited first, 3 of 3)

- [A Survey of Code-switched Speech and Language Processing](https://mlsanity.com/paper/1904.00784/) (2019)
- [See what I'm saying? Comparing Intelligent Personal Assistant use for Native and Non-Native Language Speakers](https://mlsanity.com/paper/2006.06328/) (2020)
- [Mental Workload and Language Production in Non-Native Speaker IPA Interaction](https://mlsanity.com/paper/2006.06331/) (2020)

## Abstract (arXiv)

Conversational User Interfaces such as Voice Assistants are hugely popular. Yet they are designed to be monolingual by default, lacking support for, or sensitivity to, the bilingual dialogue experience. In this provocation paper, we highlight the language production challenges faced in VA interaction for bilingual users. We argue that, by facilitating phenomena seen in bilingual interaction, such as code-switching, we can foster a more inclusive and improved user experience for bilingual users. We also explore ways that this might be achieved, through the support of multiple language recognition as well as being sensitive to the preferences of code-switching in speech output.