GetMyTrain

Learning

What commuters tell us

Every feature we ship starts as something a commuter told us was broken. Here are a few observations shaping the current build.

The apps tell me the 08:14 is on time, but not whether I should start walking. Those are different questions.
Surbiton → Waterloo
What we're doing about it: This is the core problem GetMyTrain exists to solve. Our Leave Now calculation is explicitly about the walking decision, not the timetable.
I've missed trains because the platform changed in the last minute. By the time I saw the board, the doors had gone.
Surbiton → Waterloo
What we're doing about it: Platform prediction only earns its keep when it's honest about confidence. We show 'likely' as a separate state from 'confirmed' on purpose.
When my usual train's cancelled, I don't want a notification. I want to know which train I'm actually getting now.
What we're doing about it: Alternatives need to appear in the same moment as the disruption, not as a follow-up. This shapes our alert design.
The footbridge at my home station takes me four minutes in the rain. No app knows that.
What we're doing about it: Per-station buffers matter. Our V1 uses manually curated buffers for corridor stations so the calculation reflects the real walk, not a generic one.

Got one of these stories yourself? Share it here.