The Responsive Design Trap
Most web products built for India are responsive. Almost none of them are truly mobile-first.
Responsive design means: we built it for desktop and then made it fit on a phone.
Mobile-first means: we designed every interaction assuming the user is on a mid-range Android device, on a 4G connection that sometimes drops to 3G, with thumbs as their primary input device.
These are completely different products.
The Numbers
In India right now:
- 78% of internet users are mobile-only (IAMAI 2024)
- Median Android device has 3GB RAM and a 720p screen
- Average connection speed in Tier 2 cities: 12–15 Mbps (but with high latency)
- ₹8,000–₹15,000 is the price range for the majority of smartphones in use
If your SaaS targets Indian SMEs, you are targeting users who will primarily access your product on a phone like this. Your beautiful desktop dashboard is largely irrelevant.
The EduLeap Lesson
When we built EduLeap, we spent the first week doing one thing: interviewing students in Kota and Bhilwara about how they studied.
What we found:
- They used their phones for everything. Not just browsing — note-taking, watching lectures, taking mock tests.
- They shared data plans with siblings. Every MB mattered.
- They used dark mode always. Battery life mattered.
- They expected apps to work offline for at least 30 minutes.
This research changed every decision we made.
What Mobile-First Actually Means in Code
Performance budgets: We set a hard limit of 100KB of JavaScript on the initial load. Not 1MB. 100KB. Everything else was lazy-loaded.
Offline support: We used service workers to cache the last 5 lectures and the current mock test. The app worked on a flight.
Touch targets: Every interactive element was at least 44×44px. No hover states as the primary interaction pattern.
Network-aware loading: We detected connection speed and served lower-quality video automatically on slow connections.
The Payoff
EduLeap got 42,000 students in 3 months. Their Play Store rating was 4.7/5. Their month-2 retention was 74%.
We attribute a significant portion of that to the fact that the product worked well on the devices and connections their users actually had.
The Practical Recommendation
Before your next product sprint, do this:
- Open your product on a ₹10,000 Android phone (buy one if you have to)
- Turn on Chrome's network throttling to "Slow 3G"
- Use it for 10 minutes
Whatever frustrates you is your roadmap.