“How will this make money?” is a fair question. It is just not the first question this stage of MetroPing needs to answer.
What the beta needs to validate first
Before choosing a business model, I need to know whether riders trust the alerts, use MetroPing again, and feel less need to monitor their journey.
Downloads and encouraging comments are useful, but repeat use during real commutes is stronger evidence.
Why I am taking a slow path
MetroPing is a side project, so I have chosen focused growth rather than adding features or monetisation pressure before the core journey is reliable.
A larger product is not automatically a more sustainable one. Every feature adds development, testing, support, and maintenance.
What could happen later
If the beta shows that enough riders genuinely value MetroPing, there will be time to explore a sustainable model that does not undermine the simple experience.
Being undecided now is intentional. It keeps the current work centred on product evidence instead of pretending the business questions are already solved.
Prove the value before pricing the value.
Reliability, repeat use, and a clear core problem come before a final revenue model.
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