[Macworld]

Post your comments for Why Google Maps for iPhone is good for Apple here

[David808]

It's funny how, in removing Google's entrenched place in iOS, Apple has forced Google to compete and improve. As a consumer, I think that the move by Apple is a good thing. Now, Google has no reason to hold off features they offer to Android. If they do, then the blame is on them and not Apple.

[ddbean3333]

I thought one of the complaints with Apple Maps was losing Street View. This new Google Maps app doesn't include Street View. What's the story on that feature?

[Stewsburntmonkey]

ddbean3333, on 13 December 2012 - 10:33 AM, said:

I thought one of the complaints with Apple Maps was losing Street View. This new Google Maps app doesn't include Street View. What's the story on that feature?

It does have Street View, it's just only accessible if you select a location first though. You tap and hold on the map to get a market at that location and then swipe the info card displayed at the bottom of the map up to reveal more details, including access to Street View.

[LexFriedman]

Quote

I thought one of the complaints with Apple Maps was losing Street View. This new Google Maps app doesn't include Street View. What's the story on that feature?

In fact, Google Maps does include Street View. See Dan Moren's hands-on for more.

[TheBum]

The only flaw in your argument is that, with fewer people using the Apple app, some errors that might have been reported and fixed in due course with Apple's Maps may never get reported and, therefore, not fixed.

The only saving grace is the embedded maps framework that other apps can use. Google won't be able to match that.

[AppleKiwi]

I think this is a great move for both Google and Apple. Maybe Google learned something from Microsoft's errors in the late 90s and 00's - instead of drip feeding software updates and programmes to Apple's ecosystem, they should embrace the competing OS and write decent software for it. Unfortunately, it took a big move from Apple to persuade Google to make a move like this.

Personally, I quite like Maps in iOS 6. I have downloaded Google Maps as there are times where it might be more useful, and I'm glad that consumers have a decent choice.

[WBE620]

I like the features and esthetics of the new Google Maps app, but it still falls short in my opinion. The Google Maps app does not integrate the iPhone Contacts like the old Google Maps. In my business, I am continually adding new customers to my Contact list and would navigate to their location using the Contact function in the old Google Maps. I also liked the Street View feature which the new Apple Maps does not have, so I do not want to use it. Either way I have lost functionality, and it seems Apple put profit head of servings its customers.

[JudyRay]

The map history has a record of places I have ever looked for. Years ago! I was surprised to find this info there. And yet I am not surprised.
The street view is very much up to date. I can tell because we just had a tree removed, and it is not in the picture.

[krjohnson]

I think it's much simpler; Apple made a blunder with their maps effort. That mistake could have forced buyers who needed (or just wanted) the function to switch to Android. Also, given the timing of Google's response, it seems clear they were developing the new iOS mapping program before the mess started (allowing them to play the "white knight" card).

[krjohnson]

Quote

The only flaw in your argument is that, with fewer people using the Apple app, some errors that might have been reported and fixed in due course with Apple's Maps may never get reported and, therefore, not fixed. The only saving grace is the embedded maps framework that other apps can use. Google won't be able to match that.

Saving grace for whom? The consumer? I disagree! User should be able to place the framework of their choice in that spot.

[Stewsburntmonkey]

krjohnson, on 17 December 2012 - 06:55 AM, said:

Quote

The only flaw in your argument is that, with fewer people using the Apple app, some errors that might have been reported and fixed in due course with Apple's Maps may never get reported and, therefore, not fixed. The only saving grace is the embedded maps framework that other apps can use. Google won't be able to match that.

Saving grace for whom? The consumer? I disagree! User should be able to place the framework of their choice in that spot.

Having users be able to choose a system-level mapping framework would limit the location API to be a least common denominator of the available frameworks and would have lots of legal/contractual complications.

[Mystakill]

TheBum, on 13 December 2012 - 10:45 AM, said:

The only saving grace is the embedded maps framework that other apps can use. Google won't be able to match that.

Blame Apple's app isolation restriction for that. Google has a robust set of APIs, which they can't use because apps aren't allowed to share data directly, per Apple guidelines. That's why most of the productivity apps rely on cloud storage services to provide data sharing between apps; it's a kludgy solution at best, but it's all that Apple currently allows.