Priya leaves her office in Bangalore’s Electronic City at 6:47 PM. She has exactly 43 minutes to reach the metro station at Hosa Road if she wants to catch the train that connects to the Purple Line. The company shuttle dropped her a kilometer away, as it always does. She walks past the parked cars filling what used to be a footpath, then waits. And waits. The BMTC bus that should arrive every 15 minutes does not come. An auto-rickshaw stops, but the driver wants 180 rupees for a 2-kilometer ride. She checks the Namma Metro app. The train is delayed by 8 minutes. She calculates whether she can still make the connecting bus at Majestic that will take her the final 4 kilometers home. She calculates wrong three nights a week.
This is what public transport usability means in India. Not the maps showing how extensive the metro network has become. Not the press releases announcing new corridors. The usability lives in the gaps: between the bus stop and the station entrance, between the app that shows a train coming and the reality of a platform packed with people, between the formal system that runs on schedules and the informal economy of shared autos that fills where the formal system fails.
The Architecture of a Journey
To understand Indian public transport, stop thinking about modes and start thinking about transfers. The average commuter in a major Indian city uses two to three different transport modes per trip. This is not by choice. It is because no single mode covers the full journey.
The formal mass transit layer sits at the center. Metro systems in eight Indian cities. Suburban rail in Mumbai, Chennai, Kolkata, Delhi, and Hyderabad. City bus networks run by state corporations. These systems have frequency. Delhi Metro runs every 2-3 minutes during peak hours. But frequency without integration creates friction. The metro station is rarely where you start. The bus stop is rarely where you end.
Where the Seams Split
The most obvious failure is the last mile. Fewer than 10 percent of Delhi Metro stations have formal feeder bus services. Bangalore’s metro expansion into Electronic City came with 13 feeder routes, which sounds impressive until you try to use one during peak hours. Mumbai’s new underground Line 3, India’s first fully underground metro, opened with world-class infrastructure and virtually no integrated last-mile planning.
The information gap compounds the physical gap. Real-time tracking exists in fragments. The Namma BMTC app covers 5,200 buses but does not talk to the metro app. Delhi’s DMRC app shows train arrivals but cannot tell you if the connecting bus is running. Mumbai has three separate apps for metro, suburban rail, and buses, each with their own payment systems and account requirements.
Payment fragmentation adds cost and time. Each mode requires separate tickets. The One Pune Card works on Pune Metro but not on PMPML buses. Delhi’s smart card works on the metro but not on DTC buses. A commuter transferring from metro to bus pays twice. A worker using an auto-rickshaw to reach the station pays a third time. There is no daily or weekly pass that works across modes.
The Human Cost of Fragmentation
Ramesh works security at a hospital in Hyderabad. His shift ends at 11 PM. The MMTS train he takes to reach his neighborhood stops running at 10:45 PM. He takes an earlier train, arriving at his station at 9:30 PM, then waits 90 minutes for the shared auto that will take him the final 3 kilometers home. The auto costs 40 rupees, nearly 15 percent of his daily wage. He has been doing this for three years.
The affordability trap catches people at every income level. Auto-rickshaw fares recently increased to 26 rupees base plus 17.14 per kilometer in Mumbai. A commute that requires multiple modes with separate payments becomes a significant portion of household income for working-class families.
Women navigate additional layers of calculation. Which route has better lighting? Which station has security personnel at 9 PM? Is the auto-rickshaw driver willing to go to that neighborhood? The walk to the bus stop, the wait at the stop, and the transfer between modes remain unprotected spaces.
The elderly and disabled are effectively excluded. Low-floor buses are being introduced but remain a fraction of fleets. Metro stations have elevators on paper, but many are non-functional or located at entrances that require long walks.
What Determines Usability
Four factors emerge as the true determinants of usability—not the metrics that appear in ribbon-cutting speeches.
First: transfer quality. Not the existence of an interchange, but the experience of using it. Is it one ticket or three? Is it 200 meters of sheltered walkway or a chaotic crossing through traffic?
Second: information continuity. Can a passenger see their entire journey on one screen? In Indian cities, the answer is usually no. Real-time data exists in silos.
Third: operating hours alignment. A journey that requires a metro, a bus, and an auto-rickshaw fails if any of those modes has stopped running.
Fourth: affordability across modes. A system where each transfer adds cost punishes people who live far from corridors or work in dispersed locations.
The Options Framework
Personal options exist but require knowledge and resources. Route planning apps like Chalo provide real-time information for buses in some cities. Safety apps and location sharing help women navigate risks. Choosing housing near metro corridors reduces transfer complexity, though this is a privilege of the upper middle class.
Institutional options require coordination that rarely happens. Metro corporations could integrate fares with bus agencies. Municipalities could mandate pedestrian infrastructure within 500 meters of every station. Bus agencies could align feeder service schedules with train arrivals. These are technically straightforward. They require agencies to talk to each other, which is politically difficult.
The systemic constraints are governance fragmentation and funding models that reward construction over operations. Metro projects are planned as standalone investments, measured by kilometers built and ridership targets, not by how well they connect to the rest of the system. No single entity owns the journey. Until someone does, the gaps will remain.