Re:Citymapper is what happens when you understand user exper...
by tomp on Friday August 29, 2014 @07:53AM
(#8242098)
But this just means that you should include a margin of error in arrival times when calculating which changes are possible. Doesn't excuse them from using the average time of arrival instead of the actual time of arrival each leg of the journey.
Re:Citymapper is what happens when you understand user exper...
by wrikl on Thursday August 28, 2014 @09:38PM
(#8240770)
When dealing with (London) tubes and train lines, most of the time it should be possible to indeed work out which route is actually quickest. I agree that buses do complicate things.
Re:Citymapper is what happens when you understand user exper...
by Brakenshire on Friday August 29, 2014 @12:36PM
(#8243244)
Yeah, I agree it doesn't make sense for train times, where there is a meaningful, rigid timetable (all jokes about British Rail aside).
On this question, there's a balance between possible maximum speed, and reliability. If I want to go to point B, the quickest possible route will often be made by stringing together a serious of improbable connections. For instance, the route could rely on taking three infrequent buses, with little leeway for transfer between one and another, on the assumption that they won't be slowed down by traffic (or just slow customers, stopping more than normal, etc). But if an app sends me along this route, and one of the buses is behind schedule, and I miss the connection, that then becomes a big problem. So there definitely is good sense in prioritizing frequent bus routes to some degree.