Article4 min readUpdated
Designing apps for Indian users: seven things that matter
UPI, OTP login, regional languages, mid-range phones and trust. Practical UX lessons for apps built for India, from a designer who works on them.
By Tithi Mondal, UI/UX Designer
A design that tests well in one market can fail in another. Having designed loan, tax, exam, delivery and marketplace apps for India, these are the things I now plan for from the first day.
1. Phone number first, email optional
For most Indian users, identity is a phone number. Lead with phone and OTP. Auto-read the OTP where the platform allows, show a visible resend timer, and offer a call-me fallback. Ask for an email only when you truly need one.
2. UPI is the default
Put UPI at the top of the payment options and show the apps people recognise. Then design the uncomfortable cases properly:
- Payment pending
- Money debited but order not confirmed
- User returned from the UPI app without paying
These three states generate more support calls than anything else in a commerce app. A clear message and one obvious action solve most of them.
3. Plan for more than one language
Adding Bengali, Hindi or Tamil later is harder than it sounds.
- Translated text is often longer, so buttons need room
- Indic scripts need more line height than English
- Mixed-language users expect to switch without restarting
Choosing fonts and spacing with this in mind early costs almost nothing. Retrofitting can mean redoing every screen.
4. Design for the mid-range phone
The typical device is not a flagship. That means:
- Tap targets of at least 44 to 48 pixels
- Text that stays readable in sunlight
- Skeleton loaders instead of blank screens
- Light images and no heavy animation on key screens
- Saving progress in long forms, so a dropped connection is not a disaster
5. Earn trust visibly
Where money or personal documents are involved, people look for reassurance. Show verification badges, real reviews, clear total prices before the last step and a way to reach a human. Never surprise someone with a fee on the final screen.
6. Use WhatsApp, because your users do
A "Chat on WhatsApp" support option is used far more than an in-app ticket form. Sharing an order, a listing or a referral to WhatsApp should take one tap.
7. Write the way people speak
"Authentication failed" means nothing to most people. "Wrong OTP. Please check and try again" does. Replace system language with plain words and say what to do next.
A quick test
Give your app to someone outside your team, ideally someone older and someone younger than your team's average. Ask them to complete one task while you stay silent. Every place they pause is a design problem you can now fix.
If you are building for Indian users and want a second pair of eyes on your flows, I am happy to take a look.
Frequently asked questions
What login method works best for Indian apps?
Phone number with OTP. It matches how most users identify themselves, and email can be collected later only if needed.
Why should regional languages be planned early?
Translated text is often longer and Indic scripts need more line height, so layouts designed only for English frequently break when a language is added later.
- UX
- India
- Mobile Apps