“Which city will you launch in first?” should have a specific answer. For MetroPing, that answer is Delhi NCR.
The problem started here
MetroPing came from my own Delhi Metro experience: the last-second check after reading, working, scrolling, or losing track of the stations.
Beginning where the problem was personally experienced makes the product easier to understand and the assumptions easier to challenge.
Local access improves testing
I can travel across Delhi Metro lines, reproduce reports, observe underground location behaviour, and compare an alert with what actually happened during the journey.
A local volunteer community also provides evidence across routes, phone brands, battery settings, and everyday travel habits that a simulator cannot reproduce.
One city is already a large reliability challenge
Different lines, station spacing, interchanges, underground sections, phone behaviour, and background restrictions already create many cases to test.
Adding another city too early would multiply route maintenance and support before the original promise is dependable.
Earn reliability in Delhi NCR before thinking about expansion.
A focused service area creates stronger evidence than a wide launch that cannot be tested properly.
Try it on a real Delhi Metro journey.
MetroPing is not affiliated with DMRC. Use it as an additional reminder and share honest feedback about the experience.
Try MetroPing