Every few months, a startup announces that it is building for Bharat. The press release mentions tier 2 and tier 3 cities, the next billion users, and the untapped potential of non-English-speaking India. The deck has a slide with dots in Lucknow and Coimbatore and Bhubaneswar, and the intentions are often genuine. The product, when it eventually ships, works beautifully on an iPhone in Gurgaon.
Bharat, for those unfamiliar with the term, is shorthand for the India that exists beyond the country’s major metros, the roughly 886 million people who were active internet users as of 2024, of whom 55% live in rural areas and 72% come from outside the country’s largest cities. This is the majority of India’s internet population, and it is growing faster than the urban slice, with nearly all of it, about 98%, accessing the internet primarily in languages other than English.
Many of the products built for this population are designed by teams based in India’s major metros, whose assumptions about connectivity, language, and digital literacy do not always match those of the users they hope to reach.

That is the actual problem, and it sits upstream of every specific failure that gets catalogued in design postmortems. It is not primarily a translation problem, though bad translation is everywhere. It is not merely a localization problem either, though localization is frequently an afterthought. It is an imagination problem, and it is structural. The designers, product managers, and engineers building these apps were trained on frameworks developed in Silicon Valley, schooled in case studies from American and European companies, and are themselves fluent English speakers who live in Indian metros and use high-end smartphones on reliable 4G networks. They are not lazy or malicious, but simply unable to picture, with any precision, the person they are designing for, because nothing in their professional formation required them to.
“There was one app where ‘Order Now’ was translated as ‘Abhi Aadesh Do,’” says Shruti Yadav, a product designer working on agri-tech tools in Madhya Pradesh. “Nobody talks like that. People thought it was a scam.” The word aadesh carries the register of an official command, the kind issued in a courtroom or a military briefing, grammatically correct but socially absurd, the equivalent of an app asking an American user to unironically “Procure Item Forthwith,” when ordering a mug online. The error is in the assumption that translation is a technical operation rather than a cultural one, an assumption that was never examined because the people who made it had never needed to.
This pattern repeats across every layer of product design. A search bar assumes literacy, a cart icon assumes prior experience with e-commerce, log-in code verification assumes a reliable network and a phone number that receives texts promptly, and email-based signup assumes that the user has and regularly checks an email account. These are choices that made sense for a particular kind of user in a particular context, imported wholesale into products targeting people for whom none of those conditions reliably hold.
But occasionally a product gets it right. WhatsApp, which now has roughly 535 million users in India and functions as the country’s de facto communication infrastructure, did not achieve this by targeting India specifically. It achieved it by being designed around constraints that happened to match Indian realities, among them minimal data consumption, no email requirement, voice messaging as a first-class feature rather than an add-on, and an interface simple enough to work across generations. It fit the realities of Indian users without requiring those users to adapt to it.
Most Bharat-first products have not managed the same.
“You cannot rely on minimalist design,” says Ankit Mishra, co-founder of a regional news app focused on Uttar Pradesh and Bihar. “In English apps, fewer words and clean UI means credibility. But here, users want more context. They want to see faces, videos, and explanations. More importantly, they want to see people who look like them using the product.”

The idea quickly shifts from a tech issue to a trust issue. And trust in a first-time digital user looks very different from trust in someone who has been using apps for a decade. For the latter, a clean interface signals competence, and for the former, it can signal emptiness, a space that has not bothered to explain itself.
The few companies that have genuinely cracked this have done so by treating the design constraints of non-metro India not as obstacles to work around but as the actual brief. Meesho, which now serves 213 million users with 87% of them from outside India’s eight largest cities, built its early product around the fact that its users were already conducting commerce through WhatsApp and Facebook groups, and that the trust required to complete a transaction came from personal relationships rather than polished interfaces. It did not try to teach its users to behave like e-commerce consumers. It met them where they already were. Kuku FM and ShareChat made similar calculations about content, with regional languages and voice-forward interfaces designed for intermittent connectivity and shared devices.
Changing that starting assumption requires changing who is in the room when the assumptions are made. A product team staffed entirely by urban, English-educated designers working from a Bengaluru office is going to reproduce, even with the best intentions, the imaginative limits of that room. Field research and user interviews help, but there is a difference between visiting a user and being accountable to one, and most product teams in India are accountable upward, to investors and metrics, rather than outward, to the people the product is supposed to serve.
The market for Bharat is already here. The harder task is designing as though the default user is the person holding the phone, not the person building the app.


















