[guywithabike]

One problem: It thinks that it doesn't take any time to walk from, say, Powell station to a street-level bus, so it gives you connections that you can't possibly make. This is the same problem that almost all transit apps have, unfortunately.

Edit: Also, it seems to give me really bizarre suggestions. Right now, for a trip to Alamo Square Park from downtown SF, it suggests that I take Bart from Montgomery to Powell (that's one stop) and then somehow catch Muni bus #5 in 2 minutes. A much better option would be to just take Muni bus #21 which comes past the Montgomery station in 5 minutes and heads straight to Alamo Square Park.

The quest for a good transit app continues, sadly.

Edit 2: More bizarre suggestions: From Montgomery to Alamo Square Park, it suggests this: http://imgur.com/bYLpJJI instead of taking bus #5 in 2 / 11/ or 19 minutes, which goes directly from Montgomery to Alamo Square. Also, it thinks that it takes 0 minutes to get off of Bart at 16th and Mission and make it to bus #22...

[lubujackson]

I don't see why this should be so hard. They could use Google Maps to do the walking path and then just apply a default walking speed (or even let you set yours) to calculate walking time.

[potatolicious]

Google Maps doesn't do depth or man-made obstructions to walking. The bus he's trying to catch is directly on top of the underground station, leading a simplistic walk estimator to give a near-instantaneous result. In actuality there are multiple stairs as well as a bottleneck-prone exit gate.

[khuey]

Transit apps need to implement the concept of "Minimum Connection Time" that airlines use to determine legal connections at airports.