Google maps kills the music when the voice comes on. I have to go back to music and press play again. Is there something I'm missing? Shouldn't it fade the music out, say the directions, and then fade the music back in?
Go to Tokyo (especially one of the busiest train station in the world, Shinjuku) and Hong Kong, 2 of the most densely populated cities in the world and see the difference between Google Maps and Apple Maps. You don't need a study to show that, because Apple maps basically has nothing. It's very easy to compare.
Apple's Maps will mature and be and feel the Maps application to use...Google news has been my home page for more than 10 years - unfortunately google has become the web's 800lb gorilla and like I did with Walmart (I've not been in a Walmart for five years) I determined to limit my googled life to a minimum-WHY O WHY do they feel they must "rule the world" goodbye Google...
Crappy UI for Google Maps? Seriously? It's easier, faster, and more efficient than Apple Maps.
With this said... Google Maps isn't all its cracked up to be.
I will admit that Apple Maps was very frustrating upon first release. I have never gotten wrong directions before - mainly frustrated in regards to POI search. It seemed Google was much better at producing relevant or ANY results, where as at first launch Apple only returned matches if they were a 100% match (not very good when you are unsure of a name or place).
However, this is where Apple Maps has steadily improved since its launch in iOS 6, and they now show related or relevant results that don't always 100% match the search (in a good way). So much so that Apple Maps has performed better than Google Maps in a few POI requests. When I went to Santacon in NYC this past weekend and had no idea where the "Pier 84" starting meetup was I found one such instance that supports this. Wanting to try out Google Maps I searched for it - and wasn't really given a clearcut answer to where it was.
Comically, I switched to Apple maps, searched the same entry, and got an exact and much more clearcut result. See below:
Google Maps:
Image
Apple Maps:
Image
As you can see, Google brought up "Pier 84 Supply Co". I was unsure if that was where the Pier was located, and later discovered that Google Maps had the pier labeled as a "Dog Park". If you look at Apple Maps result for the same search, it comes up with a much better answer and correctly has the pier labeled and noted as a park.
I then used Apple Maps to navigate me to the destination. It did so flawlessly and it was the first time I have relied on it 100% for turn by turn directions to get me to a place I was unfamiliar with (rather than simply testing it out on release). I was very impressed, especially with the lock screen integration and lighting the screen when directions are being given temporarily when its locked.
As such, I will definitely be using Apple Maps as my default and first-to mapping service. Hopefully I won't run into any problems, but if I do, I can just check Google quick. I would rather use Apple Maps though going forward for the improved integration and to make it better/more accurate. Not to mention, I'm not exactly a "fan" of the new Google Maps UI. I don't like how the names for the pins show up at the bottom now instead of on the pin, and to operate the app is a bit cumbersome.
git: 'off' is not a git command. See 'git --help'.
Did you mean this?
diff
The problem with Apple Maps is that for every one thing it locates correctly, there are likely 50 things it locates incorrectly. [...] I found Apple Maps to be wrong four out of five times[...]
Crappy UI for Google Maps? Seriously? It's easier, faster, and more efficient than Apple Maps.
More macrumors spin - somehow manages to represent the story as pro apple. I am very much an Apple fan but can accept their failings (and their competitor's better offerings).
So it took Apple pulling the native app for them to finally give iOS users turn by turn? I thought the native version got me lost more than Apple maps did and I am not really impressed with the new version as I think Waze or my pricey Garmin app does a much better job for me in Chicagoland personally.
The majority of iOS users might not use their smartphone for navigation at all, but still own and use a dedicated navigation device.The number of iOS 6 downloads has likely increased quite a bit over the last three months, indicating that the majority of iOS users have chosen to stick with Apple's Maps application rather than switching to Google Maps, despite the rampant complaints about the quality of the built-in app.
Wait, you start by claiming it wasn't true that Apple needed to pull the native app for Google to provide turn by turn, and then went on to show that Apple needed to pull the native app for Google to provide turn by turn.Yeah. Sure. Of course. But that's not true. Apple signed a contract with Google a long time ago that DID NOT include turn-by-turn. And guess who wrote the code for Maps when Google was the backend? Hint. It's Apple! With one year remaining in the contract, Apple wants turn-by-turn direction. Google, in turn, says sure but we also want more prominent branding and inclusion of Google Latitude in your Maps app. Apple says no. Google says no. Apple terminates the contract. Apple create its own mapping today. Google releases its Google Map now. Both companies now moved on. Apple got itself into this situation.
That's not the point. I *want* Google maps to be great. There was never a problem with it when it was the only map application on the phone. This isn't about Apple vs. Google, it's about the way the article was worded. One of the most high-profile companies in the world posts a free application that's an alternative to something that many people feel is inadequate and that's "successful?" Um, maybe if they charged $1.99 and 10 million people downloaded it, that would be successful, sure. But how is just standing around handing out free candy a "success?"Why is it so hard for some to just say - hey - that's great. I prefer Apple Maps - but it's good that those that want something else have an alternative.
No - instead it's all about having to tear the stat apart. If you downloaded it and don't use it - good for you. If you're happy with Apple maps - again - good for you. If you're happier with Google maps - again - good for you.
That's not the point. I *want* Google maps to be great. There was never a problem with it when it was the only map application on the phone. This isn't about Apple vs. Google, it's about the way the article was worded. One of the most high-profile companies in the world posts a free application that's an alternative to something that many people feel is inadequate and that's "successful?" Um, maybe if they charged $1.99 and 10 million people downloaded it, that would be successful, sure. But how is just standing around handing out free candy a "success?"
And my original point still stands... if a map app can't even search by your contacts - probably the most basic function a map app on a phone could have - how is that "successful?" It's broken just like Apple's solution is.