Slashdot Mirror
Google Backpedals On Turn-By-Turn GPS For iPhone
Smurf writes "Last October Google's Vic Gundotra announced that Google would bring turn-by-turn GPS navigation to the iPhone: 'However, Google is working with Apple on bringing it to the iPhone, and it's not ruling out licensing the software to makers of portable navigation devices used in cars throughout the world, said Gundotra, vice president of engineering at Google for mobile and developers.'
Nevertheless, after such plans were confirmed during a press conference in London yesterday, today the 'Don't be Evil' company backpedaled on them: '"We did not say we would bring it to iPhone, we said to date we've had it on Android and that in the future it may come to other platforms, but did not confirm this will be coming to iPhone at all," a Google spokesperson told PCWorld.'"
Apple is suing Googles allies, and is a rival to the Android platform. Why would Google want to help them by giving people a reason to stay locked into the iPhone when they can just get an Android phone instead? What does Google gain from people using its free apps on other platforms?
Don't be evil company did this. Don't be evil company did that.
It's like you are trying to force a contrast between Google and not-evil. Sorry if they're not the knight in shining armor from the land of dreams, but they're still a long way ahead of the competition.
Make turn by turn for the iPhone, but make it so that it directs users to drive off cliffs. Imagine the look on their faces when they realize what just happened!
I don't understand why all mobile makers are so touchy about turn-by-turn navigation.
When you've paid for the map data, and got GPS hardware in your device, it seems crazy not to implement turn by turn navigation, since the added software development cost is pretty minimal.
I suspect the problem is more of a licensing one - for example, when turn by turn navigation came out for android, it was US only for a while. A hack existed to enable it in the rest of the world, but that was soon stopped by google. Only later did it get released for the rest of the world.
Considering that it worked with a hack, it can't have been a softwatre issue that was preventing worldwide release - the only possibility is that licensing and company politics was getting in the way. Maybe people like tomtom get exclusive rights to do navigation on map data, and therefore while google has rights to use the maps, they don't have rights to do turn by turn directions with them?
"Don't be evil company did this. Don't be evil company did that."
I am one of the crazy people on Slashdot to question Google's "don't be evil" motto ending up -1 several times along with tinfoil hat jokes but I really fail to understand what kind of "evil" to reject sparing time and huge amount of money for a possibly rejected application.
Google really did good for mobile this time, at least some people from Apple will figure some companies doesn't like to be treated like a potential virus author and porn distributor.
I hadn't visited OpenStreetMaps in several years (it was an interesting project, but a little crude and sparse back then), so out of curiosity (prompted by your post) I went there to see how it has progressed. I am impressed! I don't know about how it fares overall, but someone has put an awful of work into Lexington, MA where I live. What most impressed me the most is that it includes the walking trails in the conservation land areas, which Google does not. Compare Whipple Hill on OpenStreetMap with Whipple Hill on Google Maps. (The hyperlinks are much shorter too...) So, finally I don't have to guess when I encounter partially overgrown trails on my frequents walks through them. This project needs to be more widely publicized. I had no idea how much it has improved.
Navteq belongs to Nokia
Hmmm the plot thickens. Nokia does have a major axe to grind with apple. If all google maps come from a company owned by nokia you could see them not agreeing to lic them to google for use on apple.
Some drink at the fountain of knowledge. Others just gargle.
Android has always been a predominantly Java platform and that's been known since day one.
True.
iPhone has never, ever, supported Java in any form (since Javascript is not Java as you point out) and that's also been known since day one.
True.
Nothing has changed besides a growing animosity between the companies.
False. Apple just decreed that any app written for the iPhone must be written in C, Objective-C or C++. Google has tools that translate Java into JavaScript that runs correctly on any platform. Translating Java to Objective C or C++ isn't a stretch. Apple's *new* policy disallows Google from doing that.
How anyone who isn't an Apple employee can defend that policy eludes me.