Why India never got its WeChat
For years, investors asked which company would become 'the WeChat of India' — the single app for chat, payments, commerce, and services. The honest answer so far is none. Paytm, Tata Neu, and others bolted services together top-down and found that Indian users, well served by best-in-class single-purpose apps and a neutral UPI layer, had little reason to consolidate. The lesson from those attempts is that a super app cannot be assembled by acquisition in a metro where every vertical already has a sharp standalone winner.
Why non-metro cities change the calculus
The super-app logic that fails in Mumbai works far better in a tier 2 town precisely because the standalone winners never showed up. In Solapur or Sangli, there is no dominant local taxi app, no working property portal, no structured classifieds — the verticals are empty. A single app that does several of these jobs competently is not competing against five strong incumbents; it is competing against WhatsApp groups, phone calls, and gate boards. The bundling that felt redundant in the metro becomes genuinely useful where no good single-purpose option exists.
The hard part is operations, not features
Building the app is the easy 20%; the brutal 80% is local operations across hundreds of cities. Each city needs its own supply onboarded — drivers, business listings, property inventory, sellers — and seeded from near zero. Trust is local, so a brand that means nothing in a new town has to be earned street by street through on-ground effort. The real challenge of a non-metro super app is a city-by-city go-to-market engine that can be repeated cheaply and reliably 500 times.
Designing for the Bharat user, not the metro user
Technically, a non-metro super app has to assume the opposite defaults from a metro product: budget Android phones, patchy network, vernacular over English, cash and UPI over cards, and users for whom this may be one of their first apps. The interface has to be light, forgiving, and obvious, with voice and local language as first-class inputs rather than afterthoughts. Onboarding cannot assume prior app fluency. Every design decision that a metro team treats as an edge case is the default case in Bharat.
The lessons shaping Depo
Depo's approach reflects these lessons directly: go city by city rather than launching nationally and spreading thin, lead with mobility and discovery as the high-frequency hooks, and add classifieds and property as the breadth that drives retention. Keep the product light enough for an entry-level phone, vernacular-first, and obsess over local supply before chasing the next city. The aim is not to copy WeChat but to build the right super app for Bharat's smaller cities — one whose moat is local density and trust that no metro-first player can quickly replicate.