Ghar Padharo - Case Study
Date :
Oct 19, 2024
|
Author :
Animesh
My incomplete but complete venture - GharPadharo
The Dual Identity Problem
GharPadharo began with a simple but ambitious vision: Connect students in Dehradun with trusted housing (PGs) AND trusted services (Plumbers, Tutors).
I joined as the Lead Designer to shape the logistics.
The challenge was unique: How do you build an app that is half "Real Estate" and half "Service Booking"?
Students wanted speed (Find a PG near campus).
Landlords wanted control (Verify the tenant).
Service Providers wanted gig work.
We had to blend UrbanClap (Services) with MagicBricks (Housing) without making it a cluttered mess.
The Design Approach
To solve the "Split Identity", I structured the app around Context Switching:
Discovery (Housing):
We prioritized "Distance from Campus" over generic filters.
Added "Verified Badges" to listings to solve the Trust deficit in Dehradun's unorganized market.
Booking (Services):
One-tap booking for Tutors/Cleaners.
Transparent pricing (No haggling, which is a pain point for students).
UI Logistics (The Glue):
We used neutral tones for the shell, but "Urgent Colors" for action buttons.
Tabs separated the two worlds (Housing vs Services) so the user never felt lost.
Outcome & Reflection
We successfully delivered a functional prototype that balanced these two massive ecosystems. It proved that Local Context matters—Dehradun's specific needs (Trust + Campus Proximity) required a different solution than global apps derived.
The Lesson:
I eventually parted ways with the project due to ideological differences on direction, but the lesson stuck.
Design is Negotiation.
It wasn't just about pixels. It was about negotiating Trust between a 19-year-old student and a 50-year-old landlord.
Even unfinished projects leave behind systems that last.
