Designing for Indian mobile users -- what the analytics finally confirmed
We have been pulling aggregated analytics data from client accounts for two years, looking at device type, session length, scroll depth, and conversion actions for Indian users specifically. We have twelve clients with meaningful traffic volumes, mostly small to mid-sized businesses serving customers in India. The patterns that emerged are not all surprising. Some of them overturned assumptions we had been building designs around.
I want to be careful about overgeneralising. These are twelve Indian businesses across different sectors. They are not a representative sample of the Indian internet. But for the kinds of businesses we work with, these patterns hold.
What the data confirmed
Mobile is dominant, but not evenly. Across our client base, 73 percent of sessions are mobile. But that figure varies enormously by industry. Our education client sees 89 percent mobile. Our B2B professional services client sees 52 percent mobile. Designing mobile-first is right for most of our clients, but the degree of prioritisation should match the actual split for each client's audience, not a universal assumption.
Session lengths are shorter than we expected on mobile, but conversion rates are not proportionally lower. Users are making decisions faster on mobile than on desktop. This suggests that the information hierarchy on mobile needs to surface the conversion trigger earlier, not that mobile users are lower-intent browsers. We were designing mobile pages with conversion elements halfway down the page because that is where they sat in the desktop layout. Moving them up has improved conversion rates on three of our test cases.
The tap target size issue is real and persistent. Despite years of design guidance, we still audit client sites and find interactive elements that are too small to reliably tap on a mid-range Android device held in one hand. India's mid-range Android market is enormous. Not optimising for it is a real business impact, not just an accessibility checkbox.
What the data overturned
We assumed WhatsApp click-to-chat buttons were used primarily by lower-intent users who had questions before committing. The data does not support this. WhatsApp conversions on several of our client sites show conversion rates similar to or higher than form submissions. High-intent users in India frequently prefer WhatsApp to a form, probably because the back-and-forth of WhatsApp better matches how purchase decisions happen culturally. We have made WhatsApp buttons more prominent on most client sites as a result.
We also assumed that long load times were primarily a concern for rural or low-connectivity users. They matter everywhere in our client base. Even urban users on 4G showed measurably lower conversion rates above a three-second load time. India's 4G speeds can be excellent, but they are also highly variable. Designing for excellent connectivity while half your users are on congested networks in a market town is a mistake.
The design change we have standardised
Every mobile mockup we produce now includes an explicit "thumb zone" review. Where are the primary interactive elements, and can they be reached comfortably with one thumb by someone holding a phone in the middle of doing something else? If the answer is no, we adjust before the mockup becomes a build spec.