Designing CSR Apps for Rural India: What We Learned

Gram Parivartan was one of the most humbling projects we've worked on. A CSR initiative by a large Indian corporation, the app was designed to help field workers in rural Maharashtra collect data on community development programs — water access, sanitation, education enrollment, and livelihood tracking.

The users weren't developers, designers, or tech-savvy urbanites. Many were using smartphones for the first time. Some were functionally illiterate in English. All of them worked in areas with unreliable internet.

Everything we knew about app design had to be rethought.

Our first user research session was eye-opening. Things we take for granted — swipe gestures, hamburger menus, icon-only buttons — were confusing to first-time smartphone users.

What we changed:

No icon-only buttons — Every action has a text label. We tested icon-only vs. icon+text in the field. Task completion rate went from 61% to 94% with labels added. Large tap targets — Minimum 48x48dp for all interactive elements. Many field workers used apps while standing, making precision taps difficult. Linear flows only — No branching navigation. Each screen had one primary action. Users never had to make decisions about where to go next. Confirmation everywhere — Before any submission, users see a summary screen. Data entry mistakes in the field are costly to correct later.

English was not an option for most users. We built full Marathi and Hindi support — not just translation, but locale-appropriate design.

Lessons from localization:

Text expansion — Marathi text is 30–40% longer than English equivalents. Every UI element needed to handle text overflow gracefully. Font selection matters — System fonts for Devanagari script are inconsistent across Android versions. We bundled a custom Devanagari font to ensure consistent rendering. Icons can be culturally ambiguous — A checkmark means "correct" in urban India but was interpreted differently in rural contexts. We replaced it with a thumbs-up icon after field testing. Voice input — Many users preferred speaking over typing. We integrated Google Speech-to-Text for form fields, which dramatically improved completion rates for long text fields.

Field workers often traveled to villages with zero connectivity. The app had to work entirely offline for days at a time.

We built a sync system where:

1. All data is written locally first (SQLite via Drift) 2. A sync status indicator shows how many records are pending upload 3. When connectivity is detected, sync happens automatically in the background 4. Users receive a notification when their data has been successfully uploaded

The sync notification was important. Field workers needed confidence that their day's work had been recorded. A simple "3 records synced successfully" notification reduced support calls about data loss by 80%.

Building Gram Parivartan changed how we approach product design for every project.

The users who challenged us most — first-time smartphone users in rural Maharashtra — exposed every assumption we'd built into our design process. Fixing those assumptions made us better designers for all users, not just rural ones.

The best accessibility work isn't done for edge cases. It's done because inclusive design produces better products for everyone.

If you're building for India at scale, design for the user in the village first. If it works for them, it works for everyone.