Why we built Trinetra
Nashik hosts one of the largest gatherings on earth. That's where the idea for Trinetra actually started.
Nashik hosts Kumbh every twelve years, one of the largest gatherings on earth. The ghats fill until you can't see the river. And in that crowd, every time, someone is standing still, phone in hand, lost.

We grew up here. We've been that crowd. Nashik has never lacked anything worth seeing, it's the opposite problem. The temples and ghats and small places worth knowing about are everywhere, tucked into lanes a map app flattens into grey lines. Locals know because someone once told them. Visitors have no one to ask.
So we started talking to people: pilgrims at the ghats, shopkeepers who'd given the same directions for decades, lifelong residents who hadn't seen half the city either. Everyone said some version of the same thing. Nashik has more to it than what gets shown.
Two decisions came out of that. First, we stopped trying to list everything and started curating instead.
A short, honest list beats an exhaustive one nobody trusts.
Second, we picked our audience deliberately: pilgrims with a few free hours, and travelers who came for Kumbh, or a weekend, and didn't want to leave without seeing the Nashik that isn't in the brochure.
Trinetra is live now. It's a first version, not the last word on this city, just an honest attempt at the guide we wished existed. We're still adding places, still talking to people. That won't change.
Trinetra is live on Android. Read the full story on how we built it.
Get in touch →Related reading
Story · Investors · General
Why we still build our own apps while taking client work
Most studios stop building their own products the moment client work pays the bills. We think that's exactly when you should keep building them.
Story · General
The case for building where you live
We didn't set out to build two apps. We set out to fix a gap we felt ourselves living in, and the products followed.
Story · General · Investors
Why we chose hyperlocal over broad reach for Urban Hood
We could have built a generic community app for everywhere. We built one for one neighborhood instead.