Article6 min readUpdated
Voice UI Design for Indian Users: When Voice Really Helps
Voice UI design for Indian apps: when voice helps, how to handle regional languages, voice search and voice notes, and what to test first.
By Tithi Mondal, UI/UX Designer
Suppose a farmer in a village near Bardhaman opens an app to check a mandi rate. He has mud on his hands. His phone has a keyboard in English, and he reads Bengali more comfortably than he types it. A small microphone icon in the search box could solve his problem in ten seconds. Or it could fail in a noisy field and leave him worse off.
Voice UI design is the design of an app so people can speak instead of type, and hear or read the result clearly. It includes the microphone button, the listening state, the way spoken words appear as text, and what the app does when it misunderstands. In India, where many people use more than one language and many use mid-range Android phones, voice can be a real help. It can also be a trap if designed carelessly.
When does voice actually help in an app?
Voice helps when typing is hard, slow or unsafe, and when the task is short. It does not help when the task needs precision, privacy or a long list of choices.
Here is a plain comparison.
| Situation | Voice helps? | Why |
|---|---|---|
| Searching for a short item name in your own language | Yes | Typing in a regional script on a small keyboard is slow |
| Entering a 12 digit account number | No | One wrong digit causes a problem; the user needs to see it |
| Using the app while riding or cooking | Yes | The hands are busy |
| Entering a password or OTP | No | Others can hear it |
| Reading out a long menu of options | No | Screens show many options at once; voice shows one at a time |
| Leaving a message for a seller or a teacher | Yes | A voice note is faster than typing |
The pattern is simple. Voice is good for short input in natural language. It is weak for exact data and private data.
How should voice input work for regional languages?
Voice input for regional languages should let the user choose the language of speech, show the recognised words immediately, and allow a quick edit. Never assume that the language of the phone is the language the user will speak.
A few decisions matter here:
- Ask for the speech language once. A user may have an English phone and speak Hindi. Put a small language chip next to the microphone, such as "Hindi" or "Bengali", and remember the last choice.
- Show words as they are recognised. Seeing the text appear tells the user the app is listening and lets them stop early if the words are wrong.
- Allow editing. Put the recognised text in the normal search box, so the user can fix one wrong word instead of speaking everything again.
- Plan for mixed speech. Many people mix English and regional words in one sentence, such as a Bengali sentence with "order" and "payment" inside it. Test with that kind of speech, not only with clean sentences.
How well a speech tool understands a language depends on the language, the accent, the phone and the noise. I will not claim a number here. Test with real speakers from the place your users live, in the places they use the app. Then decide which languages to support first. My article on regional language app design in India covers the text side, and Bengali typography in UI and logo design covers how the script should look on screen.
How do you design voice search in apps?
Voice search should be a microphone button inside the existing search box, with a clear listening state and results that appear on the same results screen as typed search. Do not build a separate voice screen with different results.
Build it in this order:
- Place the microphone icon at the right end of the search box, at least 48 pixels wide to tap, so a thumb can hit it.
- On tap, show a bottom sheet with the text "Listening" and a moving line, so the user knows the phone heard the tap.
- Fill the recognised words into the search box as they come.
- After the user stops speaking, run the search and show the normal results.
- If nothing is heard, say "I could not hear you. Please try again, or type." and keep the keyboard one tap away.
Use the same filters and sorting that typed search uses. For more on those, read search and filter UX design. Also ask for microphone permission only when the user taps the microphone for the first time, with one line that explains why. Asking at app launch makes people refuse.
Are voice notes in apps a good idea?
Voice notes are a good idea when users need to explain something that is awkward to type, such as a problem with a delivery, a lesson doubt or a message to a seller. They need clear controls for recording, playing and deleting.
In a marketplace or a learning app, a voice note can lower the barrier for users who do not like typing. The screen needs to cover these points:
- A large record button that works with press and hold, plus a tap-to-lock option for longer notes.
- A visible timer and a limit on length, so the file does not become too big for slow networks.
- A playback bar with a speed option, so the receiver can listen faster.
- A short text label or transcript when possible, so a person in a quiet office can read instead of listening.
- A delete and re-record option before sending.
Also consider data cost and storage. Audio files are larger than text, and many users have limited mobile data. See designing for low-end phones and slow networks for how to keep an app usable in those conditions.
What goes wrong with voice, and how do you plan for it?
Voice fails in noise, with unfamiliar accents, in public places and when the user speaks a language the tool does not handle well. The design must give a way forward each time, which is always the keyboard.
Plan for these cases:
- Noise. If the app hears nothing useful, say so plainly and offer typing. Do not keep a dead microphone screen open.
- Wrong words. Show what was heard and let the user fix it. Never act on a spoken payment amount without a visual confirmation.
- Privacy. Tell the user when the microphone is on, and what happens to the recording. If the app stores voice data, explain it in plain language, and ask a qualified professional about the rules that apply to your product.
- Accessibility. Voice can help users who find typing hard, but it can exclude users who cannot speak clearly. Offer both ways. My guide on accessibility in app and web design goes deeper.
- First-time users. Many users have never used voice input in any app. Add a short example, such as "Say: tomato price today", in the listening state. See designing for first-time internet users.
What should you test before adding voice to your app?
Test whether real users in your target area complete a task faster by voice than by typing, in their own language, in the places where they use the app. If voice is not faster or more comfortable for them, leave it out.
A simple test needs 5 or 6 people and a phone. Give each a task, such as "find the price of onions" or "send a note to the seller". Let them choose voice or typing. Watch where they hesitate. Record which language they speak and whether the app understood. Do this before you spend money on development. My article on usability testing on a small budget explains how.
If you want voice planned properly inside the flows of a mobile app, my mobile app design service includes mapping where voice fits and where the keyboard should stay, and you can get in touch to talk through your product.
Frequently asked questions
Does voice search work for Hindi and Bengali?
It depends on the speech tool, the accent and the noise around the user. Test with real speakers from your target area before you promise it in the app.
Should voice replace the keyboard in my app?
No. Voice should sit beside the keyboard. Noise, privacy and accents make voice fail often enough that users always need a typing option.
When should an app ask for microphone permission?
Ask when the user first taps the microphone, with one line that explains why. Asking at app launch, before the user sees any benefit, makes many people refuse.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.