Fine, them keep paying as us until you get it right. iPhone users don't care about the voice we care about street view.
I personally prefer the Voice and the Flyover to StreetView. Never was a fan of the SV. Only time I used it was when I was house hunting and wanted to get a feel of the outside of the house. I never use it for directions.
Quote:
Originally Posted by drobforever
I do not believe this. I mean, look, if Google ever make a Maps App for iOS, there will be turn-by-turn navigation. So, what's the point for google to hold it back? No point.
It's more believable that Apple axed the old Maps App because Google wants the data wired to them in a certain way and Apple thinks that'd give Google too much advantage. It's ok to axe it because of competitive reasons, I don't blame Apple. But I don't buy this turn-by-turn thing, and the facts will confirm what I said once Google finally releases a Maps App for iOS with turn-by-turn navigation.
Well they hold it back to tout an Android feature that iOS doesn't have. IMO Google will release their own app when Apple gets theirs right. They probably figure that all the bad press, and pissed off users (with "no option" so they believe) will get some people to switch over to Android.
Google's not that quiet nice guy at the corner of the party. They are just as ruthless as Apple and MS and any other successful corporation. They want to win, and at the same time eliminate competition.
[" url="/t/152914/disagreements-over-turn-by-turn-directions-prompted-apple-to-ditch-google-maps#post_2199035"]Yesterday I criticized Apple, but today I'm going to criticize Google, based on this new information.
Google basically told all Apple users to go and F*ck themselves. No, we will not provide voice guided navigation for Apple users, we want it exclusively for Fandroids. Apple users have to look at their screens while driving, and if they crash their cars and die, then too bad.
And remember, Google Maps app on iOS was also not vector based.
So then Apple told Google to go F*ck themselves, because Apple realized that they had no choice but to release their own Maps app.
The Apple Maps app has a very strong foundation, it's fast, it's smooth and it's vector based. As the Apple map app improves, with more and better data, then it will be quite good. Soon, 99% of all normal people, besides a few moronic Fandroids, will have forgotten all about Map-Gate, just as people have forgotten about all of the other "Gates" that came before that.
.
I don't believe it was that at all and agree with Quadra 610. Google was protecting a key feature of their platform.
I do not believe this. I mean, look, if Google ever make a Maps App for iOS, there will be turn-by-turn navigation. So, what's the point for google to hold it back? No point.
Apple never gives Mac software more features than their Windows equivalents…
The purpose of holding it back is to get Android converts.
Turn by turn on an iOS device is not that useful. Unless you have dedicated mounting brackets in your auto so that the device is more at eye level, using turn by turn and looking down at the device sitting on the passenger seat or holding your phone while driving is a dangerous habit to get into. Personally, I have built in navigation in all my autos so I don't need it at all. I can see a case for all vehicles having built in navigation within the next 5 years or so. Perhaps this new Apple Maps service is the precursor to striking a deal with auto makers to provide built in iOS devices in the cars..
Some cars already have this integration. I believe Ford's Sync feature can use a smartphone's navigation capabilities, and GM's MyLink is likely to incorporate the capability soon. I'm not familiar with at what level these work, but the concept is clearly out there. The navigation option is a pretty big revenue generator, though, so there's competing interests. My car has downloadable turn-by-turn but I skipped the in-dash navigation. With my iPhone, I haven't missed it at all.
First of all i%u2019m a 61 year old male and i don%u2019t see as well as i used to. last spring i was surprised to find that i had not got the memo and they changed the Triborough bridge to the rfk bridge. this caused me to get a bit lost at night in the bronx.%u201D Perfect, flawless%u201D google maps on my i phone apparently thought that it was more important for me to see an unbroken blue line than the street name under it . in this cell challenged neighborhood my blue position dot was lets say slow in updating and the drivers in this neighborhood did not lets say appreciate me slowing down trying to read (some missing) street signs to determine where i was . google maps almost cost me my life and were terribly frustrating. i tried apple maps today and the search is a bit rough but once it was established where i wanted to go the huge direction balloons were a great help especially easy to read at a glance while driving . I am a 3-d cad designer and i could see the problems with the bridges were that the program that renders the flyover was having problems interpreting where the bridge ended and the shadow begins as the shadows were shifting around on moving water! I hardly think this is apples fault and a reasonable person would understand that the bridge and the Eiffel tower are still ok. I am glad to have apple mapping and i know apple is working as fast as they can to improve it and i do not think they should have delayed its inclusion .
I hope Apple ensures Google go through intense review for the proposed Google Maps standalone app and in the mean time improve their Maps App and say a big FU to Google. 100 Million customers no longer using your app,is not a small number.
Google can not longer hold Apple to ransom and thats what Page and the gang were trying to do.
Not just '100 million,' but likely the highest income segment customers of anyone/anywhere on the globe. It's suicidal to give that up, especially when monetizing mobile is where the future is for companies like GOOG and FB. (As an aside, I don't know anyone who's halfway well-off -- who also is not an Apple-hater -- that's an Android user).
Google was protecting a key feature of their platform.
Yes, a feature that they didn't want Apple to have. That's their choice of course, but no matter how you cut it or slice it, we now know why Apple had to dump Google and go with their own version.
Fine, them keep paying as is until you get it right. iPhone users don't care about the voice we care about street view. Siri can't hear us on a street anyway to give us directions at least not in Manhattan.
Please don't speak for all iPhone users. Personally, I didn't realize that street view was an option on iOS until I read stories about the Google maps app being removed from iOS. Using the Google maps app on an iPhone 4S with Verizon was an exercise in frustration as the maps loaded extremely slowly. Apple's maps app is much faster on the same hardware in the same locations.
Apple doesn't license most of their key technologies/patents to competitors, for any amount of money. In fact, they'll defend them to the death first.
Google can't be expected to act any differently.
In general, there's some truth to that.
HOWEVER, when Apple refuses to license its core technologies, they're not screwing their own users. They're keeping the competition from getting Apple technologies. Google, OTOH, by refusing to release a good Maps app for iOS or license the technology to Apple is screwing their own users.
Besides which, Google didn't have to be Apple's competitor. Apple was apparently quite happy with partnering with Google until Google copied all of their technologies and set themselves up as a competitor (even though Google is apparently making less money than they would have if they had never gotten into the Android thing at all).
Essentially, Google invited a good friend over for dinner, stabbed him in the back and then said "I'm not going to help you because you're bleeding all over my living room".
That's the whole point. You just listen to what it tells you "Turn left at 300 meters". No need to look down at it. I've used it on Apple Maps and it's pretty darn good.
Sure my vehicles all have turn by turn voice but they also have visual cues on screen as well, just like the iOS app. The problem is unless you put the iOS device in the back seat you are going to be tempted to look at the screen. If the screen is not at the eye level position, it is dangerous, because you take your eyes too far from the road, for too long, and too often. The Apple app even gives you a big warning before you start using it.
So, essentially, Apple wasn't willing to negotiate anything, which proves me right, this was done for political reasons alone, not concern for the customers.
First of all i%u2019m a 61 year old male and i don%u2019t see as well as i used to. last spring i was surprised to find that i had not got the memo and they changed the Triborough bridge to the rfk bridge. this caused me to get a bit lost at night in the bronx.%u201D Perfect, flawless%u201D google maps on my i phone apparently thought that it was more important for me to see an unbroken blue line than the street name under it . in this cell challenged neighborhood my blue position dot was lets say slow in updating and the drivers in this neighborhood did not lets say appreciate me slowing down trying to read (some missing) street signs to determine where i was . google maps almost cost me my life and were terribly frustrating. i tried apple maps today and the search is a bit rough but once it was established where i wanted to go the huge direction balloons were a great help especially easy to read at a glance while driving . I am a 3-d cad designer and i could see the problems with the bridges were that the program that renders the flyover was having problems interpreting where the bridge ended and the shadow begins as the shadows were shifting around on moving waterI hardly think this is apples fault and a reasonable person would understand that the bridge and the Eiffel tower are still ok. I am glad to have apple mapping and i know apple is working as fast as they can to improve it and i do not think they should have delayed its inclusion .
If you link back to the source article and read it there's not a claim that Google wouldn't offer Turn-by-Turn navigation to iOS users under any circumstances according to their sources. Instead it's says that if they did Google wanted certain things from Apple in return and Apple wasn't biting.
<p style="margin-bottom:.45em;border:0px;font:inherit;vertical-align:baseline;color:rgb(51,51,51);font-family:Georgia, serif;line-height:24px;">"But according to people familiar with Google’s thinking, the search giant, which had invested massive sums in creating that data and views it as a key feature of Android, wasn’t willing to simply hand it over to a competing platform.</p>
<p style="margin-bottom:.45em;border:0px;font:inherit;vertical-align:baseline;color:rgb(51,51,51);font-family:Georgia, serif;line-height:24px;">And if there were terms under which it might have agreed to do so, Apple wasn’t offering them. Sources tell <strong style="margin:0px;padding:0px;border:0px;font:inherit;vertical-align:baseline;">AllThingsD</strong>
that Google, for example, wanted more say in the iOS maps feature set. It wasn’t happy simply providing back-end data. It asked for in-app branding. Apple declined. It suggested adding Google Latitude. Again, Apple declined."</p>
Sure my vehicles all have turn by turn voice but they also have visual cues on screen as well, just like the iOS app. The problem is unless you put the iOS device in the back seat you are going to be tempted to look at the screen. If the screen is not at the eye level position, it is dangerous, because you take your eyes too far from the road, for too long, and too often. The Apple app even gives you a big warning before you start using it.
There actually is a solution for this: buy velcro stickers and an iPad case; glue the stickers to your dashboard and case, and drop the iPad case on them. When you park, just remove the iPad and store it in the glovebox. You can use the lighter adapter to power the iPad, so it can stay always on displaying Google Maps, and you don't need to tap a button on the screen since you can center the screen in your current position and follow the blue line (or find your way back to it, or reset directions, if for some reason you miss an exit).
Apple should have implemented its own MAP solution years ago when they heard that Google was going to encroach on their turf and build a mobile phone which is similar in design.
With so much cash in hand, Apple should have invested in building its own services and don't let Google snap up all the great app developers one by one.
Sure my vehicles all have turn by turn voice but they also have visual cues on screen as well, just like the iOS app. The problem is unless you put the iOS device in the back seat you are going to be tempted to look at the screen. If the screen is not at the eye level position, it is dangerous, because you take your eyes too far from the road, for too long, and too often. The Apple app even gives you a big warning before you start using it.
Well, I suppose if you use it that often you can get a windshield or dashboard mount. There are many on the market.
Without voice turn by turn any GPS app is nearly useless in a car society like the U.S. This makes a lot of sense and without that feature I rarely if ever even used the Google maps and instead relied on Mapquest and Waze. I wish they had at least extended the contract for one more year and included the Apple maps not as the default but as an additional app to use until it improves, but no real loss for me since I drive and absolutely need voice directions.
Comments
Quote:
Originally Posted by iSheldon
Fine, them keep paying as us until you get it right. iPhone users don't care about the voice we care about street view.
I personally prefer the Voice and the Flyover to StreetView. Never was a fan of the SV. Only time I used it was when I was house hunting and wanted to get a feel of the outside of the house. I never use it for directions.
Quote:
Originally Posted by drobforever
I do not believe this. I mean, look, if Google ever make a Maps App for iOS, there will be turn-by-turn navigation. So, what's the point for google to hold it back? No point.
It's more believable that Apple axed the old Maps App because Google wants the data wired to them in a certain way and Apple thinks that'd give Google too much advantage. It's ok to axe it because of competitive reasons, I don't blame Apple. But I don't buy this turn-by-turn thing, and the facts will confirm what I said once Google finally releases a Maps App for iOS with turn-by-turn navigation.
Well they hold it back to tout an Android feature that iOS doesn't have. IMO Google will release their own app when Apple gets theirs right. They probably figure that all the bad press, and pissed off users (with "no option" so they believe) will get some people to switch over to Android.
Google's not that quiet nice guy at the corner of the party. They are just as ruthless as Apple and MS and any other successful corporation. They want to win, and at the same time eliminate competition.
I don't believe it was that at all and agree with Quadra 610. Google was protecting a key feature of their platform.
Quote:
Originally Posted by Apple ][
Yesterday I criticized Apple, but today I'm going to criticize Google, based on this new information.
Same here. If this story is true, Google can go **** itself.
I am willing to wait for an improvement in Apple's map app over time.
That said, Apple could do a far better job of explaining this to users.
Originally Posted by drobforever
I do not believe this. I mean, look, if Google ever make a Maps App for iOS, there will be turn-by-turn navigation. So, what's the point for google to hold it back? No point.
Apple never gives Mac software more features than their Windows equivalents…
The purpose of holding it back is to get Android converts.
Quote:
Originally Posted by mstone
Turn by turn on an iOS device is not that useful. Unless you have dedicated mounting brackets in your auto so that the device is more at eye level, using turn by turn and looking down at the device sitting on the passenger seat or holding your phone while driving is a dangerous habit to get into. Personally, I have built in navigation in all my autos so I don't need it at all. I can see a case for all vehicles having built in navigation within the next 5 years or so. Perhaps this new Apple Maps service is the precursor to striking a deal with auto makers to provide built in iOS devices in the cars..
Some cars already have this integration. I believe Ford's Sync feature can use a smartphone's navigation capabilities, and GM's MyLink is likely to incorporate the capability soon. I'm not familiar with at what level these work, but the concept is clearly out there. The navigation option is a pretty big revenue generator, though, so there's competing interests. My car has downloadable turn-by-turn but I skipped the in-dash navigation. With my iPhone, I haven't missed it at all.
Quote:
Originally Posted by souliisoul
I hope Apple ensures Google go through intense review for the proposed Google Maps standalone app and in the mean time improve their Maps App and say a big FU to Google. 100 Million customers no longer using your app,is not a small number.
Google can not longer hold Apple to ransom and thats what Page and the gang were trying to do.
Not just '100 million,' but likely the highest income segment customers of anyone/anywhere on the globe. It's suicidal to give that up, especially when monetizing mobile is where the future is for companies like GOOG and FB. (As an aside, I don't know anyone who's halfway well-off -- who also is not an Apple-hater -- that's an Android user).
Quote:
Originally Posted by dasanman69
Google was protecting a key feature of their platform.
Yes, a feature that they didn't want Apple to have. That's their choice of course, but no matter how you cut it or slice it, we now know why Apple had to dump Google and go with their own version.
Quote:
Originally Posted by iSheldon
Fine, them keep paying as is until you get it right. iPhone users don't care about the voice we care about street view. Siri can't hear us on a street anyway to give us directions at least not in Manhattan.
Please don't speak for all iPhone users. Personally, I didn't realize that street view was an option on iOS until I read stories about the Google maps app being removed from iOS. Using the Google maps app on an iPhone 4S with Verizon was an exercise in frustration as the maps loaded extremely slowly. Apple's maps app is much faster on the same hardware in the same locations.
In general, there's some truth to that.
HOWEVER, when Apple refuses to license its core technologies, they're not screwing their own users. They're keeping the competition from getting Apple technologies. Google, OTOH, by refusing to release a good Maps app for iOS or license the technology to Apple is screwing their own users.
Besides which, Google didn't have to be Apple's competitor. Apple was apparently quite happy with partnering with Google until Google copied all of their technologies and set themselves up as a competitor (even though Google is apparently making less money than they would have if they had never gotten into the Android thing at all).
Essentially, Google invited a good friend over for dinner, stabbed him in the back and then said "I'm not going to help you because you're bleeding all over my living room".
Quote:
Originally Posted by twosee
That's the whole point. You just listen to what it tells you "Turn left at 300 meters". No need to look down at it. I've used it on Apple Maps and it's pretty darn good.
Sure my vehicles all have turn by turn voice but they also have visual cues on screen as well, just like the iOS app. The problem is unless you put the iOS device in the back seat you are going to be tempted to look at the screen. If the screen is not at the eye level position, it is dangerous, because you take your eyes too far from the road, for too long, and too often. The Apple app even gives you a big warning before you start using it.
Wait so google wanted something in return for providing Apple with more data?
Apple turned them down, well their demands must of been outlandish, right?
So what did google want?
-For the app to be called google maps and for the inclusion of Latitude, and location check in service.
What else?
-According to reports nothing else.
Did they ask to build the app themselves, and have complete control over it?
-No apple would still make the app, and improve it how they see fit.
I see
.
We'll use your data and your turn by turn directions but the user will never know it.
Google will be the one losing out most.
Google makes revenue from Apple users. Less Apple users using Google's services = less money for Google.
There actually is a solution for this: buy velcro stickers and an iPad case; glue the stickers to your dashboard and case, and drop the iPad case on them. When you park, just remove the iPad and store it in the glovebox. You can use the lighter adapter to power the iPad, so it can stay always on displaying Google Maps, and you don't need to tap a button on the screen since you can center the screen in your current position and follow the blue line (or find your way back to it, or reset directions, if for some reason you miss an exit).
With so much cash in hand, Apple should have invested in building its own services and don't let Google snap up all the great app developers one by one.
Quote:
Originally Posted by mstone
Sure my vehicles all have turn by turn voice but they also have visual cues on screen as well, just like the iOS app. The problem is unless you put the iOS device in the back seat you are going to be tempted to look at the screen. If the screen is not at the eye level position, it is dangerous, because you take your eyes too far from the road, for too long, and too often. The Apple app even gives you a big warning before you start using it.
Well, I suppose if you use it that often you can get a windshield or dashboard mount. There are many on the market.
Or you can just use one of these haha!
Without voice turn by turn any GPS app is nearly useless in a car society like the U.S. This makes a lot of sense and without that feature I rarely if ever even used the Google maps and instead relied on Mapquest and Waze. I wish they had at least extended the contract for one more year and included the Apple maps not as the default but as an additional app to use until it improves, but no real loss for me since I drive and absolutely need voice directions.