As more people tested MetroPing, useful feature requests kept arriving. Saying yes felt helpful, but every yes also made the product larger and harder to trust.
The hidden cost of one more feature
A new feature creates development, testing, battery and performance considerations, bugs to maintain, and another decision for users.
That cost continues after launch because the feature has to survive future devices, operating-system updates, and changes elsewhere in the app.
The filter I now use
Before building anything, I ask: does this directly help the user avoid missing a destination or interchange?
If the answer is no, I save it for later. I have also removed features that distracted people from starting the journey reminder.
Why less fits MetroPing now
MetroPing is a side project following a slow and focused growth path. More features can come after the core experience is reliable and the user base grows.
For now, protecting one clear purpose is more valuable than making the roadmap look large.
Sometimes building less creates a better product.
The strongest product work can be choosing not to add something that weakens the main experience.
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