Designing for India's scale

Most design advice is written for a user who does not live here. That user has a good phone on a good network, and years of practice with software. Design for India and the assumptions fall away. The phone is a few years old and short on storage, on a network that comes and goes. For many people, the screen in front of them is the first computer they have ever operated.

The second thing that changes is arithmetic. India does nothing at small numbers. A decision that would be a footnote in most markets lands here on more people than many countries hold. At this scale an interface decision does not affect a few users. It includes or excludes millions.

A policy nobody writes down

A nine-tap flow is not a UX nitpick. It is a policy about who gets to use the thing. Every extra tap is paid for in someone's data and someone's confidence, and the people with the least of both (opens in new tab) are the first to drop away. Nobody writes that policy down. It ships silently, inside the interface.

When there is no leaving

I have seen both halves of what this means. On a consumer super app, the market grades you instantly. Organising dozens of services into one screen only works if every screen keeps its promise, because a person who loses momentum does not complain. They leave.

On national public services the grading is harsher, because there is no leaving. A citizen cannot take their pension to a competitor. Whatever we ship is the only door there is, and if it will not open on an old phone with a weak signal, it is not a door. It is a wall with a handle.

Earn the trust first

The order of work changes. Reliability beats delight. A form that works every time on a cheap phone does more good than a beautiful app that stutters, and boring but bulletproof beats beautiful but fragile. None of that is an argument for ugliness. Function leads, and a simple interface can and should be beautiful. It is an argument about sequence: earn the trust first, then earn the smile.

Here is the part that surprises teams: designing for the hardest conditions makes the product better for the easiest ones (opens in new tab). Strip a flow down until it survives a weak signal and it becomes faster for everyone. Write the error message for a first-time user and the expert reads it in half a second. The constraint is not a tax on the design. It is the discipline that produces it.

That is what India's scale does to the job. It removes the comfortable fiction that design decisions are small. The interface decides who a product is actually for, and here that decision is never private: it lands on millions of people at once, most of whom will never know a decision was made. The only honest response is to make it on purpose.