News for hackers. Stuff that matters.
Re:How Google Builds Its Maps by czhiddy on Thursday September 06, 2012 @08:11PM (#4487023)
> So I have no clue why on earth Apple created such a neutered mapping app for a mobile device.

The terms of the license agreement with Google for maps data likely didn't include the ability to perform turn-by-turn navigation. Another reason why they moved to their own maps backend for iOS 6.

Re:How Google Builds Its Maps by kalleboo on Friday September 07, 2012 @02:28AM (#4487877)
What I read was that Google would allow Apple to do turn-by-turn in exchange for ads. Apple don't want to sully iOS with ads so they refused those terms, and Google wouldn't agree to anything else.
Re:How Google Builds Its Maps by rogerchucker on Thursday September 06, 2012 @09:18PM (#4487230)
Does that mean by the time Google had decided to work on the iPhone-like Android interface, they had been planning to work on a turn-by-turn navigation system using Google Maps for Android as well?
Re:How Google Builds Its Maps by no_more_death on Thursday September 06, 2012 @10:01PM (#4487350)
Android has had turn-by-turn navigation at least since 2010. Having a GPS is irrelevant if you've got an Android.
Re:How Google Builds Its Maps by abruzzi on Friday September 07, 2012 @10:48AM (#4489351)
Actually it depends on how you use GPSs. Its certainly possible to write a mapping/GPS app for a smart phone that is competitive with the more advanced features of handheld or dashmount GPSs, but I simply haven't seen one yet. None of the features I need are big ones, but rather a bunch features that add up to a much better user experience for a GPS geek. A couple of those hard to find features are: multi point routing (or some way to allow me to tell the GPS the route instead of the other way around), ability to build routes on PC/Mac and upload to the GPS, off-road routing, track to route conversion, etc..