RailYatri & IntrCity SmartBus
Improving booking, reliability, and security across five production Android apps.
I initiated booking-funnel and reliability improvements while leading two developers across five live Android apps. RailYatri and IntrCity had 5M+ combined total users; I raised IntrCity's crash-free usage from 92% to 98% and took RailYatri from a failed government security audit to a pass in ten days.
Project evidence
- ~26%
- wider program's cumulative funnel improvementTwo-year team and program outcome; my contribution included three directly tracked Android experiments and client instrumentation.
- 5M+
- combined total product usersRailYatri and IntrCity combined; product scale across two consumer apps.
- 92% to 98%
- IntrCity crash-free usageImprovement over roughly six to twelve months and 20+ releases.
- 10 days
- failed government security audit to passLive RailYatri app; I implemented nearly all fixes for roughly 15 findings, with one teammate.
01 / Initiative at production scale
Improve the products while staying responsible for five live apps.
I built and maintained five production Android apps, including RailYatri and IntrCity SmartBus with 5M+ combined total users. I initiated work on booking conversion and reliability alongside the architecture, UI, networking, local persistence, testing, debugging, and release responsibilities.
I led two developers and stayed hands-on with the code, keeping modernization, experiments, and reliability connected to an ongoing production release schedule.
02 / Product and business impact
Turn booking hypotheses into measurable Android experiments.
I initiated booking-funnel improvements and implemented Android A/B variants, interaction-event instrumentation, and experiment logic across IntrCity booking flows, including three directly tracked experiments.
My Android work contributed to a wider two-year product and design program associated with roughly 26% cumulative home-to-payment conversion improvement. I owned the client variants and measurement that made hypotheses releasable and results observable within that program.
System model
Production modernization across five applications
Work spanned legacy Java modernization, architecture, reliability, security review response, and production releases across a five-application Android portfolio.
Main sequence with a security branch
- 01Existing Java code
Production features across five applications
- 02Java to Kotlin
Modernize substantial legacy code
- 03Stronger architecture
MVVM/MVI · Flow · Room · modular Gradle
- 04Profile and observe
Crash and reliability evidence
- 05Security review response
Remediation and passing reassessment
- 06Production releases
Ship architecture and reliability improvements
Connections
- Existing Java codeJava to Kotlin
- Java to KotlinStronger architecture
- Stronger architectureProfile and observe
- Profile and observeProduction releases
- Security review responseProduction releases
03 / Architecture under load
Use architecture and production evidence to raise reliability.
I initiated reliability improvements, investigated failures through profiling and observability, and modernized substantial legacy Java code to Kotlin. I strengthened the architecture with MVVM/MVI patterns, Coroutines/Flow, Room/SQLite, and modular Gradle while production releases continued.
I raised IntrCity's crash-free usage from 92% to 98% over roughly six to twelve months and 20+ releases. Production evidence guided the work, connecting architectural changes to the stability of an app customers were already using.
04 / A ten-day security response
Take a failed government security audit to a pass in ten days.
The live RailYatri app failed a government security audit. I took responsibility for the Android remediation, implemented nearly all fixes for roughly 15 findings with one teammate, and brought the app to a passing reassessment in ten days.
I coordinated implementation and reassessment under the deadline while the app remained live.
05 / Hands-on leadership
Lead the team and remain accountable for the production result.
I led two developers across architecture, implementation, debugging, code quality, and releases, while continuing to investigate production issues and ship changes myself.
Booking experiments, modernization, reliability, and security were connected responsibilities across the same live portfolio. Keeping that whole picture in view helped me coordinate delivery and stay accountable for what happened after release.
Discuss the work
Bring me the next product problem.
I bring product judgment, hands-on leadership, and the engineering depth to take an important problem from the first decision through release. Let’s talk about what you want to build or improve.
The source code is proprietary to RailYatri (Stelling Technologies). I can discuss my responsibilities, architecture, testing strategy, security work, technical decisions, trade-offs, and outcomes without disclosing confidential material.