[jakelazaroff]

> This is all much worse on the Android app as well, where it makes the assumption that your use case is to get from where you are right now to somewhere else.

That strikes me as a fantastic assumption. I wonder what percentage of routes involve the user’s current location? I bet it’s high!

[eitland]

Yep. But it used to be even better when it made that assumption clear by adding a pre-filled box with your current location.

It just worked for the default case but when you needed something else it was straightforward to do that.

[StavrosK]

Doesn't it? It gives me two boxes, "current location" and "destination" and I can change either.

[wccrawford]

I can't reply to eitland for some reason, but yes, I get both those boxes.

I open the app, click my destination, and then click "Directions". The very next thing is both of those boxes, with "current location" defaulting to the start location. I can then change that if I want.

It optimizes for my most common use case, but allows me to do it otherwise, too. I don't think I could design this better.

[eitland]

Straight away after you open Google Maps on a mobile?

[StavrosK]

No, I open it, look for the destination, then press directions and can edit the starting point.

[eitland]

Then we agree. I find that utterly annoying since I've seen how simple it could be but it seems many people disagree with me :-)