Voice Interaction
A human-computer interaction paradigm in which voice serves as the primary input and output modality, emphasizing natural language expression and hands-free operation. It relies on technologies such as ASR, NLU, and TTS.
Timeline (last 90 days)
The value of voice interaction is not in replacing the keyboard but in creating a sense of presence; taking AI out of the laptop screen can significantly shorten the psychological distance of interaction.
Progress of large models in semantic understanding and generation has moved voice interaction from 'being able to understand' toward 'being able to converse and complete tasks'.
Voice will not simply replace keyboards and touchscreens, but will complement them.
The shortcomings of voice interaction include: privacy and social awkwardness issues in public places, relatively high correction costs in precise input scenarios, insufficient context understanding in multi-turn dialogue, and robustness to accents and noise remaining an engineering challenge.
As computing devices move from desktops to earphones, watches, in-car systems and home spaces, screens and fingers are no longer always available, and voice has natural advantages in these scenarios: hands-free operation, low learning cost and fast expression speed.
Voice and gesture interaction will continue to improve, but for the foreseeable future, the keyboard will remain the preferred input method for most people when handling complex information tasks.
Voice suits short sessions, high context, and low-precision tasks; text suits long documents, high precision, and traceable tasks.
Fowler believes voice interaction should be treated as an independent design medium rather than a voiced version of a text interface; merely replacing a text box with a microphone button is not the correct approach to a voice product.
Updating delivery instructions by voice may cause problems such as address ambiguity and time window conflicts.
The shortcomings of voice interaction in shopping scenarios include list visualization, confirmation of complex subscription terms, and status feedback after delivery instruction changes being inferior to screen interaction.
11 more timeline events
All Facts (20)
Voice interaction in the developer tools domain is still in an exploratory stage, facing unique technical challenges such as technical terminology recognition, code-switching phenomena, noisy environment adaptation, and disambiguation.
60%UnverifiedThe value of voice interaction is not in replacing the keyboard but in creating a sense of presence; taking AI out of the laptop screen can significantly shorten the psychological distance of interaction.
50%UnverifiedVoice will not simply replace keyboards and touchscreens, but will complement them.
50%UnverifiedProgress of large models in semantic understanding and generation has moved voice interaction from 'being able to understand' toward 'being able to converse and complete tasks'.
50%UnverifiedAs computing devices move from desktops to earphones, watches, in-car systems and home spaces, screens and fingers are no longer always available, and voice has natural advantages in these scenarios: hands-free operation, low learning cost and fast expression speed.
50%UnverifiedThe shortcomings of voice interaction include: privacy and social awkwardness issues in public places, relatively high correction costs in precise input scenarios, insufficient context understanding in multi-turn dialogue, and robustness to accents and noise remaining an engineering challenge.
50%UnverifiedVoice suits short sessions, high context, and low-precision tasks; text suits long documents, high precision, and traceable tasks.
50%UnverifiedFowler believes voice interaction should be treated as an independent design medium rather than a voiced version of a text interface; merely replacing a text box with a microphone button is not the correct approach to a voice product.
50%UnverifiedThe shortcomings of voice interaction in shopping scenarios include list visualization, confirmation of complex subscription terms, and status feedback after delivery instruction changes being inferior to screen interaction.
50%UnverifiedUpdating delivery instructions by voice may cause problems such as address ambiguity and time window conflicts.
50%UnverifiedVoice interaction is linear and instantaneous; users do not lay out background information all at once the way they do when typing, and half-sentences, references and topic jumps are common.
50%UnverifiedVoice interaction latency is the watershed of experience; engineering must push end-side latency down to where users do not perceive it.
50%UnverifiedUsers' tolerance for waiting in voice interaction is far lower than in text interfaces, and latency is the issue most easily underestimated by independent developers and small teams.
50%UnverifiedVoice information is sequential and non-persistent; once a sound is played it dissipates, and users must rely on internal memory to retain information.
50%UnverifiedIn pure voice interaction, when information arrives in rapid bursts, the human brain's working memory cannot keep up, making it a suboptimal way to convey information.
50%UnverifiedThe fundamental difference between voice interaction and web requests is that making users wait briefly for a web request is generally acceptable, whereas silence in a telephone scenario is misinterpreted as a dropped call.
50%UnverifiedVoice interaction breaks both premises of traditional authorization: the absence of visual information undermines the validity of informed consent, and blurred action boundaries mean agents may misinterpret casual responses as authorization signals.
50%UnverifiedVoice interaction has been widely accepted on mobile devices and smart speakers, but remains at an early stage in desktop work environments.
50%UnverifiedIn open-plan office environments, voice input may introduce privacy and disturbance issues.
50%UnverifiedIn human conversation, pauses exceeding 200 milliseconds are perceived as 'hesitation'.
50%