Onboarding & UX Guide · 11 min read
India's next 400 million internet users are not delayed versions of Metro India users — they're a different audience with different devices, different connectivity, different financial literacy, and different relationships with technology. Products designed for the IIT graduate in Bangalore will consistently fail in Nashik, Varanasi, or Dharwad unless the team explicitly designs for the difference. This guide covers what those differences are and how to design for them.
Digital literacy: Can use apps with clear visual cues. Reads Hindi fluently but struggles with English financial terms ("AUM", "NAV", "XIRR"). Voice-comfortable — prefers talking to typing. Makes decisions based on what his trusted contact recommended, not app store ratings.
Digital literacy: Comfortable with social apps. Nervous about financial apps — afraid of "doing something wrong and losing money." Will read every screen before tapping anything. Will call customer care if confused rather than retry. More likely to abandon than make a mistake.
Test every release on a Redmi 9A or Samsung M12. If your animation lags on this device, cut it. If your screen is crowded on a 4.7-inch display, simplify it. The flagship phone your design team uses creates false confidence about how the product actually feels to your median user.
Design every flow to handle network interruption gracefully. Save form state locally before submitting. Show meaningful offline states — not just a spinning loader. Cache critical content. For payments specifically, never show a "processing" screen that could mean either success or failure — Bharat users will retry, causing double transactions. Always show a definitive success or error state, even if it's delayed.
"Annualised Returns" → "Yearly Growth." "NAV" → "Price per unit today." "SIP" → "Monthly investment." "KYC Verification" → "Quick ID check." Every piece of jargon is a micro-abandonment risk for first-time users. Run a plain-language audit on every screen — if a 12th-grade student in a Tier 3 town can't understand it without googling, rewrite it. This isn't dumbing down; it's precision communication.
Apps that add Hindi, Tamil, or Telugu consistently see 30–60% improvement in activation rates for those language segments. Start with the languages that match your largest underperforming geography. Use professional translation (not Google Translate) for all transactional copy — payment confirmation, error messages, and KYC instructions. Poor translation in high-stakes moments destroys trust irreversibly. String length varies significantly across Indian languages — test all layouts in each language before shipping.
The bottom 60% of the screen is where all primary actions should live. Put the most-used buttons, CTAs, and navigation items in the natural thumb reach zone. Top-of-screen actions require two hands or a grip shift — Bharat users on crowded buses, in markets, and on construction sites are overwhelmingly one-handed users. This also applies to text input — large touch targets (minimum 48dp), large keyboards, and OTP auto-fill are not polish; they're accessibility.
In Metro UX conventions, red = error or warning. In Bharat financial contexts, red = loss of money. Using red for routine informational warnings ("your session is about to expire," "incomplete form") triggers financial anxiety disproportionate to the actual situation. Use amber/yellow for warnings. Reserve red exclusively for genuine error states involving money or identity.
A significant percentage of new internet users are more comfortable speaking than typing. Enable Google Voice Input on all text fields (this is OS-level and requires no custom development). For search specifically — add spoken search support and handle incomplete phonetic spellings gracefully. "Zerodha" is easy to type when you know how to spell it. It's easy to mispronounce in 6 different ways when you learned about it from a friend.
For KYC, document upload, payment flows, and any multi-step process — use illustrated step-by-step visuals, not written instructions. A diagram of "hold your Aadhaar card like this, ensure the 12-digit number is visible, take photo in good light" converts 35–45% better than the same content written as bullet points. BYJU's animated explanations and PhonePe's animated QR code examples exist because they work for this audience.
Metro users assume app-store-featured apps are legitimate. Bharat users don't — they've heard enough WhatsApp fraud stories to be suspicious of everything new. Establish trust proactively: show SEBI/RBI/IRDAI registration numbers on onboarding screens, show the number of users and the CS phone number in the first session, use testimonials with real names and cities that sound like their city. Don't just show a padlock icon — explain what it means in plain language.
When Bharat users hit a problem, they go to WhatsApp — to ask the friend who recommended the app, to find the company's WhatsApp number, or to share a screenshot of the error. Build a WhatsApp support channel before building an in-app chat. Make the WhatsApp number clearly visible on error screens and in the help section. Bharat users who get a response on WhatsApp within 2 hours have dramatically higher retention than those routed through ticket-based email support.
"They'll figure it out — our Metro users did." Metro users had higher digital literacy, more time to learn, and more tolerance for confusion. Bharat users who get confused don't debug — they call the friend who recommended the app or they uninstall. Confusion tolerance is much lower because the stakes feel higher (it's their money) and the recovery path (calling support) is more effortful.
"We'll add Hindi support in the next version." By the time you add it, the Bharat market has gone to a competitor who offered it from day one. Activation in a language a user isn't confident in produces permanently lower lifetime value — even if you add the language later, the first experience anchors the user's confidence in your product.
"Bharat users are price-sensitive, not feature-sensitive." Bharat users are trust-sensitive and simplicity-sensitive first, price-sensitive second. A product that charges slightly more but is simpler and feels safer will beat a cheaper but confusing product every time in this segment. Price competition is a symptom of failing to differentiate on trust and usability.
We test products with Tier 2/3 users and identify the exact friction points killing activation and retention in non-Metro markets. Book a free session.
Book Free Session