Students can't find voice input
97% knew it existed. 71% still typed.
Discoverability fixes
Voice sessions per daily user
01The question
Indian students are heavy, mobile-first ChatGPT users, yet few use voice input. The usual assumption is that they can't find it. I set out to test that, alongside four other explanations.
02What I found
- DiscoverabilityRuled out. 97% already knew voice existed.
- Social discomfortConfirmed. Average comfort was 3.82 out of 5 alone, and 2.06 in a library or shared space.
- Preference for typingStrongly confirmed. 71% still preferred typing, mostly because it's faster (12 mentions) and gives more control (10).
- PrivacyPartly. Present, but secondary to fit with how they work.
- Accent and Hinglish recognitionPartly. A barrier for a few, not most.
"I use voice only when my hands are busy." "I don't want people around me hearing my queries." "For assignments and coding, I still prefer typing."
03The proposal
Stop treating voice as a general alternative to typing, and anchor it to moments where it clearly wins. Suggest it when hands are likely busy or during a commute, and when someone hesitates on an empty text field. Let people edit the transcript before sending, which addresses the control problem directly.
04What I rejected, and why
- Discoverability fixesBigger mic buttons and first-launch tooltips solve a problem that 97% of respondents don't have.
05How I'd measure it
Voice sessions per daily user
the main metric, for the segment that sees contextual suggestions.
- Share of sessions where the mic is tapped
- Share of voice inputs sent without cancelling
- Share of users who use voice again within 7 days
Total messages per user don't fall. Voice should add usage, not replace typing.
06Limits of this research
Thirty-four students is enough to rule out the discoverability assumption with confidence. It isn't enough to size the opportunity, and it says nothing about non-students.