Hmm. Making your app profitable by running a fleet of buses seems a bit... ambitious.
Background: Everybody in London uses Citymapper and nobody uses Google Maps. It is a great app. London Buses are also very good. As has been pointed out, they have GPS sensors. There is also a sophisticated infrastructure behind them, e.g. a control room that tells drivers to turn around and go back mid-rout if the buses are too unevenly distributed. See e.g. the BBC's Route Masters documentary if you can find it: http://www.bbc.co.uk/programmes/b02znsx2
As has also been pointed out here, London Transport does not make a profit (although their public funding is constantly shrinking). So any new entrant has to be more profitable than them with a much smaller market share. Wonder if that is possible if you only differentiate yourself by technology. We'll see.
> There is also a sophisticated infrastructure behind them, e.g. a control room that tells drivers to turn around and go back mid-rout if the buses are too unevenly distributed.
Yeah, it's really sophisticated; it means that if I catch a 3 bus signed for Crystal Palace there's about a 33% chance that it dumps me in Brixton to wait an extra twenty minutes in the rain, instead of taking me all the way home.
I'm pretty sure the described tactics should succeed at optimising expected travel time, but they (knowingly) do so at the cost of variability.
I regular get to experience the opposite: waiting 20min in the rain, at which point three busses arrive as a group.
Yet another extreme is low variability with high scheduled travel time, achieved by including a minute of slack at every second stop or so.
It's a result of an inherent instability in bus operations: As soon as the intervals diverge only marginally, faster busses become even faster, because there are fewer people waiting for them and vice versa.
In my experience, Google Maps is really terrible outside the United States. It doesn't seem to understand that in the UK, a narrow country lane might have a speed limit of 60 mph, but nobody could ever drive that speed on it. It's constantly proposing insane detours off A roads onto back lanes obstructed by sheep and farm equipment.
Unlike Citymapper, Google Maps doesn't have a notion of multimodal transport: cycling to a train station, for example. Citymapper also doesn't "lose" your in-progress journey if you click the wrong thing or close the app.
Maybe they don't have enough Android-carrying traffic on rural lanes to calculate an average speed?
All I know is I frequently get really goofy route suggestions from Google Maps that seem totally clueless about the difficulty of driving narrow UK backroads.
> Google maps uses average speed on roads to estimate the fastest route, not the speed limit.
Even in the U.S. Google Maps regularly recommends things like unprotected left turns against heavy traffic to get onto a road with a speed limit which is 5-10mph higher, even when that road is equally congested.
Google Maps still doesn't have any concept of Boris Bikes either, London's bike rental scheme that's been active and popular for 5+ years. CityMapper has shown real-time bike and slot availability for years, as well as travel time estimates, to the point where I doubt any Londoner would bother using the official app anymore for bike rental (or any of the other third party apps).
"Unlike Citymapper, Google Maps doesn't have a notion of multimodal transport: cycling to a train station, for example"
This is really neat. Also includes Uber-ing to a train station.
Ah yes, Google maps which either thinks I want to take three transfers to avoid walking 1km at the beginning and end of my trip, OR cycle the whole way, but that having a bike which can cover that 1km is preposterous.
"Everybody in London uses Citymapper and nobody uses Google Maps."
Well I live in London and actually prefer Google Maps directions over CityMapper which I think is slow to start and a bit slow in fetching and updating alternative routes.
I do like the "preferred tube car" to use based on your entry / exit tube station but after a while you don't need the actual app for this as they don't change.
I feel like London is just the test city since it's where their offices are. Maybe the plan is to fine-tune the platform here and then expand to cities which are not as well served by public transport?
Background: Everybody in London uses Citymapper and nobody uses Google Maps. It is a great app. London Buses are also very good. As has been pointed out, they have GPS sensors. There is also a sophisticated infrastructure behind them, e.g. a control room that tells drivers to turn around and go back mid-rout if the buses are too unevenly distributed. See e.g. the BBC's Route Masters documentary if you can find it: http://www.bbc.co.uk/programmes/b02znsx2
As has also been pointed out here, London Transport does not make a profit (although their public funding is constantly shrinking). So any new entrant has to be more profitable than them with a much smaller market share. Wonder if that is possible if you only differentiate yourself by technology. We'll see.