Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
And I still remember all too well how Google refused to add turn by turn navigation in their ios app, until Apple released Maps. I'll never forgive them for that and will always tilt towards other options when possible.
This is so wrong. Google wanted more customer data from Apple and Apple refused. So Google didn’t permit vector mapping or turn by turn navigation on the iOS app. This led Apple to making their own. There’s more to the story than what you’re saying.
 
  • Like
Reactions: Westacular
Google owns Waze. Waze has been doing this forever. What’s the difference between the two and why switch? Not trashing google just honestly asking why make two identical apps

They both look and work quite different. Google uses the traffic data and reports from Waze, yet both apps use different routing mechanisms and of the two I personally prefer Google suggested routes (easier to drive along). The interface alone might be a determining factor for quite a few people.
 
They both look and work quite different. Google uses the traffic data and reports from Waze, yet both apps use different routing mechanisms and of the two I personally prefer Google suggested routes (easier to drive along). The interface alone might be a determining factor for quite a few people.

It's actually nice to have three different navigation apps with different algorithms. When traffic is well and truly ****ed, you can query Apple Maps, Google Maps, and Waze to see which one has the best route. When two out of the three agree, that's probably the best option. :)
 
I’ve learned to trust the routing in Waze, even when its suggested route seems illogical. Too many times I’ve ignored those little suggested reroutes through surface streets I normally wouldn’t consider and been burned for it. I find Waze’s routing and estimated travel times to almost always be most accurate, so while the app’s design and style isn’t my favorite, it’s the best navigation solution I’ve used. They’ve done a good job with its integration in CarPlay as well.

Now if I need POI searching or walking directions, I always turn to Google Maps.

for me Apple Maps ETA is the more precise, but routing is not the fastest.
Google Maps is most of the time Fastest... it tends to overestimate the time by a few minutes for my daily drive to/back from work even if I follow the speed limit.
Waze ETA is usually accurate... but it pushes me to routes outside of the Highway way more often than it should... and this often leads to additional time behind the wheel because it didn't "see" the trafic on the other roads.
 
This is so wrong. Google wanted more customer data from Apple and Apple refused. So Google didn’t permit vector mapping or turn by turn navigation on the iOS app. This led Apple to making their own. There’s more to the story than what you’re saying.
What's the "so wrong" part?
 
  • Like
Reactions: IGI2
And I still remember all too well how Google refused to add turn by turn navigation in their ios app, until Apple released Maps. I'll never forgive them for that and will always tilt towards other options when possible.
That's because Apple didn't allow apps that offered turn by turn into the app store. Apple's fault bro, not Google.
 
Google didn't have their own iOS app until after Apple released Maps because Apple DID NOT ALLOW IT, plain and simple.

The Maps app in iOS has always been Apple's. Back when it used Google Maps, it was really Apple's app using Google's data. Google did not write nor maintain that app, and it shipped as part of iOS. The refusal to have turn by turn directions in that app was Apple's, not Google's.

Only once Apple Maps came about did they finally allow Google to write their own Maps app; as far as I'm concerned that was the best thing that ever happened for Google Maps on iOS because they were extremely stifled before by Apple's refusal to let them write the app.

I don't mean to be combative, I just get tired of people getting the history behind this wrong. Apple was the bad guy here, not Google.

quote your source please.
 
I vividly remember Google releasing their first iOS Maps app some time after iOS 6 came out with Apple Maps.

Before that, Google did not have their own Maps app on iOS. The "Google Maps" in iOS was an Apple-created app and its lack of features was on Apple.
This makes me think of issues with Apple Music on Android.

I took up EE offer of 6 months free Apple Music.
Poor user xperience on Android compared to Spotify.

1. Main playback screen with album art and playback controls does not rotate to landscspe. Optimum phone orientation when on gym equipment.

2 One cannot swipe right or left on the album art to change tracks

3 when listening to a curated playlist one cannot jump to the album a track came from. Very poor.

4 No gapless playback. Seriously!!!
This ruins an album like Dark Side Of The Moon.

There are other irritations compared to Spotify.

There is no way I would pay for Apple music compared to Spotify.
 
Google owns Waze. Waze has been doing this forever. What’s the difference between the two and why switch? Not trashing google just honestly asking why make two identical apps
They did not make Waze, the bought it
 
I vividly remember Google releasing their first iOS Maps app some time after iOS 6 came out with Apple Maps.

Before that, Google did not have their own Maps app on iOS. The "Google Maps" in iOS was an Apple-created app and its lack of features was on Apple.

If you have a link to information that disputes this, please post it because I don't recall any sort of alternative Google Maps app for iOS before iOS 6 came out. I'm quite curious myself if I'm actually wrong, it's just that my own memory completely supports what I wrote.

https://www.theguardian.com/technology/2012/nov/05/apple-google-maps-iphone-dropped

I'm working so I'll try to find better info later. Apple used Google maps for navigation prior to releasing Apple Maps. They didn't renew their license and dropped them to release Maps. Google then had to get their Maps app, as third party, as opposed to the default, approved... whuch they did. The above linked article briefly touches on the fact that Google refused to allow turn by turn on IOS... something that frustrated Apple. And frustrated a lot of people like me... who at that time were using Google Maps... on IOS.. to navigate. And their was a lot of discussion at the time about its lack of turn by turn. It's both amusing and frustrating to have people tell me now that there was no Google navigation prior to maps. There was, and I used it. I was happy when Apple dropped licensing from them and released their own...because I knew that competition was good. And it worked. Google added turn by turn in their third part stand alone app...

edit: to those of you feel strongly that there was no Google Maps prior to Apple Maps... read the linked article. and answer me this: Why did the Guardian write an article in November 2012 (when Apple Maps was released), with the headline being "Why Did Apple Drop Google Maps..."

edit 2: And here is another article talking about Google Maps RETURNING to Apple.

https://www.engadget.com/2012/12/12/google-maps-ios-app/


[doublepost=1538428009][/doublepost]
This is so wrong. Google wanted more customer data from Apple and Apple refused. So Google didn’t permit vector mapping or turn by turn navigation on the iOS app. This led Apple to making their own. There’s more to the story than what you’re saying.

You are right that their are two sides to every argument. You then put your foot in your mouth and say that my side of the argument is completely wrong (thus saying your side is the only side). I used navigation extensively prior to Apple maps. So it's frustrating to see people on here claim no such navigation existed prior to Apple Maps. And I had watched the discussion at the time with a lot of interest. You can try to parse more blame on whomever you want... but for whatever reason Google did NOT wish to license turn by turn to Apple. So Apple went solo. Then voila... within a year they release their app with turn by turn.

https://www.theguardian.com/technology/2012/nov/05/apple-google-maps-iphone-dropped
[doublepost=1538428133][/doublepost]
They did not make Waze, the bought it

They also didn't make Google maps... they bought it.
[doublepost=1538430804][/doublepost]
That's because Apple didn't allow apps that offered turn by turn into the app store. Apple's fault bro, not Google.

Read the article I linked to, that discussed how Apple tried to get Turn by Turn in Google maps... and Google wouldn't allow it. And where are you getting your info that Apple wouldn't allow turn by turn apps... can u link a source please?
 
Last edited:
  • Like
Reactions: BugHunter and IGI2
I used Waze for a little bit because my Speedo was broken in my car, Waze shows the speed! But it does look too cartoonist!

I like Waze because it has warnings to alert me to police ahead… I'm sure that has saved me money. Also, it seems to have better traffic information, because the eta estimate seem to be more accurate. But what I hate about it is that when I get close to the destination, I can’t tell where the building I’m trying to find is that, often times I can’t even tell what side of the street it is on. With Apple Maps, it seems to show much better wear in a parking lot or what not a building is located. As far as accuracy, I seem to think that Apple Maps is slightly better than Waze. But when I have problems then I go to Google Maps which seems more accurate than both. No one is perfect… I have had occasions were all three take me to the wrong location. I think anyone that claims to only use one or that one is perfect is probably exaggerating.
 
They also didn't make Google maps... they bought it.

Not true. They bought Keyhole for mapping and satellite data, but plenty of even the original Google Maps (tiled map pixel images fetched via AJAX) was developed in-house.
 
19MB over a 530 mile trip doesn't sound all too bad, when you consider that along the route, the app has to download map data for the towns and such that you drive through and near. Google Maps will do the same thing.
Indeed, I thought it was incredibly low. The point I was trying to make was that I reckon it is thanks to the basic graphics, I bet the colourful Google maps app uses more.
 
Indeed, I thought it was incredibly low. The point I was trying to make was that I reckon it is thanks to the basic graphics, I bet the colourful Google maps app uses more.

Ahh, I see.

It's been about the same in my experience. Just make sure you don't leave *satellite* imagery on when running Google Maps; that WILL eat a lot more data for obvious reasons! (Source: Burned a few gigs Miami to Orlando once)
 
  • Like
Reactions: CarpalMac
Not true. They bought Keyhole for mapping and satellite data, but plenty of even the original Google Maps (tiled map pixel images fetched via AJAX) was developed in-house.

I was basing my saying that off this:

https://en.m.wikipedia.org/wiki/Google_Maps

Specifically... "Google Maps began as a C++ desktop program at Where 2 Technologies. In October 2004, the company was acquired by Google, which converted it into a web application. After additional acquisitions of a geospatial data visualization company and a realtime traffic analyzer, Google Maps was launched in February 2005.

But I'm open minded... if you can source me more accurate info I'll hear you out :)
 
I was basing my saying that off this:

https://en.m.wikipedia.org/wiki/Google_Maps

Specifically... "Google Maps began as a C++ desktop program at Where 2 Technologies. In October 2004, the company was acquired by Google, which converted it into a web application. After additional acquisitions of a geospatial data visualization company and a realtime traffic analyzer, Google Maps was launched in February 2005.

But I'm open minded... if you can source me more accurate info I'll hear you out :)

It appears I stand corrected!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.