I wish it would quit treating two places with identical names as equally relevant no matter what their relative distances. Gee Google, did I want the one that's ten miles away or the one that's 186 miles away? Being able to say "take me to the Home Depot that's beside a Walmart" would also be nice.
My personal pet peeve, though, is the absolute and deliberate refusal of Google to voice-type the word "o'clock." It is bizarre, and I say it is deliberate because it's not confusing it for another word. No, you can stand there and say o'clock over and over again, and the circle will keep pulsing indicating it's listening to you, but it will type nothing. It's infuriating because it stops you from being specific. You say "start at four-fifteen" and Google knows to type "start at 4:15". But if you say "start at four o'clock" you just get "start at 4" and there's not a damned thing you can do about it. You can say "We'll go at one o'clock, two o'clock, four o'clock, five o'clock" and it just types "we'll go at 1245"
My personal pet peeve, though, is the absolute and deliberate refusal of Google to voice-type the word "o'clock." It is bizarre, and I say it is deliberate because it's not confusing it for another word. No, you can stand there and say o'clock over and over again, and the circle will keep pulsing indicating it's listening to you, but it will type nothing. It's infuriating because it stops you from being specific. You say "start at four-fifteen" and Google knows to type "start at 4:15". But if you say "start at four o'clock" you just get "start at 4" and there's not a damned thing you can do about it. You can say "We'll go at one o'clock, two o'clock, four o'clock, five o'clock" and it just types "we'll go at 1245"
Why?!