A lot of design advice quietly assumes a user with a recent iPhone, fast Wi-Fi, English as a first language and plenty of storage. Design for that person in India and you'll build something that looks great in a review meeting and struggles in the hands of the people who actually use it.
India isn't one user. It's many languages, a huge range of devices and network conditions, and habits shaped by apps that already work well for people, especially WhatsApp. Ignoring that context doesn't make a product global. It makes it fragile.
I run a UI/UX design studio in India, and some of our most rewarding work has been for Indian users, including Pukaar.ai, a doctor-led co-parent for a baby's first year that supports parents in several Indian languages. Here's what I've learned, and what I'd check on any product built for India.
Start with the real person, not the average one
On Pukaar.ai, our primary persona was Aarti Sharma, "The Anxious First-Timer": 29, a software engineer in India, first baby at three months, Android and WhatsApp-first. It's 2 a.m., the fourth wake-up of the night. She needs a plain sentence first, reasoning she can check, and a visible way out.
Notice what that persona tells you. She is tech-literate, yet the product still had to be simple, because context matters more than capability. And she is Android-first and WhatsApp-first, which shapes almost every interaction decision.
What I'd do on any Indian product:
- Build personas from interviews, not assumptions. Pukaar.ai's research included 70+ user interviews and a community of 400+ parents.
- Record device, language preference and messaging habits as part of every persona.
- Design for the stressful moment, not the calm demo.
Languages: more than translation
Supporting multiple Indian languages is not a find-and-replace job on your strings file. It changes layouts, tone and even which words you should use in English.
Practical rules for multilingual UI
- Design for text expansion. Labels in some languages can run much longer than in English. Use Auto Layout and avoid fixed-width buttons.
- Test real scripts. Devanagari and other Indian scripts have different heights and line spacing needs from Latin text. Check that your typeface supports the scripts you ship, or pair it with one that does.
- Let people switch language easily, and remember their choice. Don't bury it three levels deep in settings.
- Respect code-mixing. Many people naturally mix English and Hindi. Sometimes the English word ("doctor", "feed", "report") is clearer than a formal translation nobody uses in daily speech.
- Write plain first, translate second. Simple English translates far better than clever English. My post on plain language UX writing covers how.
Tip
Before you lock a typeface, type a few real Hindi labels into your layout. Many popular Latin fonts have no Devanagari at all, and the fallback font can look badly out of place.
Voice can bridge gaps
Voice reduces the burden of typing and reading for many people. On my own site, Sage, my AI assistant, supports chat and real-time voice in English and Hindi. Building it taught me a lot about tone, turn-taking and what happens when people switch languages mid-sentence, which I cover in what I learned designing a voice AI assistant.
WhatsApp habits shape expectations
For many Indian users, WhatsApp is where conversations, support, groups and updates already happen. Your product is being compared to it, whether you like it or not.
On Pukaar.ai, a WhatsApp community channel was part of the research itself: real 2 a.m. questions and polls from parents, with 50+ queries a day before launch. That channel showed us the exact words parents use and the moments they reach out.
What this means for design:
- Conversational patterns feel natural. Chat-style interfaces, like Pukaar.ai's companion QARA, meet people in a format they already trust.
- Sharing is a core feature. Make it easy to share a report, a receipt or a booking to WhatsApp. Pukaar.ai offers a detailed PDF of answers, which is easy to forward to family or a doctor.
- Families are part of the flow. Decisions are often shared. Pukaar.ai's Caregiver feature lets parents invite family or a nanny with limited access, using roles like Father, Mother, Nanny and Guardian.
- Consider WhatsApp as a channel, not a replacement. Notifications or support via WhatsApp can be helpful, as long as people opt in.
Watch out
Don't message people on WhatsApp who didn't ask for it. A channel they trust turns into spam quickly, and they'll block you there too.
Budget phones and patchy networks
Design reviews usually happen on fast laptops and flagship phones. Many of your users won't have either.
Device checklist
- Test on a low-cost Android phone with a smaller screen and modest memory, not just in the Figma preview.
- Keep tap targets generous and primary actions in the bottom third. Pukaar.ai's 2 a.m. rule was one-handed use and oversized tap targets. See designing for one hand.
- Choose typefaces with clear figures and good legibility at small sizes. On Demerara Bank we picked Red Hat Display partly because it stays legible on budget phones, and the same thinking applies here.
- Keep contrast strong. Cheaper screens and bright outdoor light wash out subtle greys.
Tip
Keep one inexpensive Android phone at your desk and check every build on it over mobile data, not office Wi-Fi.
Network checklist
- Show useful content before everything loads, and use skeletons instead of blank screens.
- Save drafts locally so a dropped connection doesn't wipe a half-filled form.
- Give clear, honest states when offline, with a retry action.
- Keep the app size and downloads lean. Storage on budget phones fills up quickly, and big apps get uninstalled first.
Local formats and trust cues
Small details tell people a product was made for them.
| Detail | Use | Avoid |
|---|---|---|
| Currency | The rupee symbol with Indian grouping: ₹1,50,000 | ₹150,000, or a dollar sign left over from a template |
| Large amounts | Lakh and crore where users think in them | Millions and billions only |
| Dates | DD/MM/YYYY | MM/DD/YYYY |
| Time | IST by default | UTC or a US time zone |
| Phone numbers | +91 prefilled with a 10-digit field | A generic international field with no default |
- Phone-first sign-in: OTP login via mobile number is a familiar pattern. Make the OTP field auto-read where the platform allows, and keep resend timers visible.
- Familiar payment flows: people are used to quick UPI payments, so a long, card-only checkout will feel slow.
- Visible humans: in health and finance, showing real experts builds trust. Pukaar.ai's doctor booking lists verified paediatricians by rating, price and availability, with an emergency under-15-minute slot pinned on top.
Work with us
Need an app designed? Our mobile app design agency takes iOS and Android apps from first flows to launch-ready screens.
Key takeaways
- Build personas from interviews and record language, device and messaging habits.
- Multilingual design means flexible layouts, real-script testing and plain source copy.
- WhatsApp sets expectations: design for conversation, sharing and family involvement.
- Test on budget Android phones and poor networks, not just flagships and Wi-Fi.
- Local formats like ₹1,50,000, DD/MM/YYYY and OTP sign-in quietly build trust.
Building for India?
The Pukaar.ai case study shows these ideas in a real product used by Indian parents, from the persona to the final screens. If you want to try a bilingual voice experience, talk to Sage in English or Hindi. And if you're building for Indian users and want a second pair of eyes, email me.