Apple maps is terrible.

[rocketpig]

superchunk said:

rocketpig said:

superchunk said:

As for the map errors and what you'll take... I'm betting a TON of non US users would disagree with you as they lost all functionality with this new map app. Not just errors, but entire cities and countries.

Should Google have delayed the release of services like Google Drive? Should they have scrapped the project entirely? Because, after all, it was buggy as shit on launch day and it cost me hours of productivity as I tried to adopt the system and integrate it into my workfolow. It was basically useless to me (worse than useless, actually) and I PAID MONEY FOR IT.

But no, I accepted the fact that I was a launch day customer and that systems often release with bugs. I waited out the 2-4 weeks it took them to shore up the service's deficiencies and now, I'm a happy Google Drive customer.

Pretty much the same thing applies to when I upgraded to Mountain Lion on launch day (in retrospect, a rather stupid decision on my part). It was buggy, it pissed me off, I waited it out and now it's a pretty great OS. I've also had these experiences with EVERY version of Windows (which I've been using since Win95).

In short, shit happens. If this is still a problem in two months, then I'll start complaining. The long-term benefits of an Apple-created Maps application FAR outweigh the short-term negatives of buggy software.

There is a difference between going from nothing to a new app that has issues and going from a fully functional map system to a nothing.

As for OS upgrades...yeah bad decision. I always wait for it to get at least one service pack. (talking Win of course)

I am a software dev. I know it happens and very large complex systems will have issues day one. However, in this instance you have a product that had a perfectly function application. You had Apple a nearly infinitely wealthy company that could have purchased 100% of its map data from mapquest or some other large company before launch. There are 100s of other scenarios where it could of at least matched what they were taking away from their customers with the forced removal of Google's maps. They could have rolled it out in chunks, i.e. US first, then other nations as their map data was within some degree of what Google had.

But they didn't. Even in the US there are serious issues like directions to Sea World San Diego that take you to the island across from the park. I'm not talking about the 3D, which has crazy imaging issues.. but real data like directions or simply wrong roads/maps entirely.

Apple f'ed its customers. It should have realized they were removing significant functionality for a very large part of their userbase and that should have been the priority NOT removing Google.

You honestly don't think that Apple bought up a slew of data for their maps system already? Where do you think they found all the data they currently have in the system?

If that data is buggy (which it obviously is), then they have to shore up that information. The problem is that you don't KNOW it's buggy until you put it in the wild with millions of users. No development team can do a comprehensive check of a system this massive.

Again, we're back to "Apple needed users". Should they have beta-tested the software? Yeah, I think that would have been a good idea. I mean, why not? But now that it's out, they have to fix the problem (which, AGAIN, is being overblown by the Internet in typical dogpile fashion). The application hasn't erred for me and I even started a thread for it on VGC, which garned one response of "it didn't properly parse center/centre".

In the long-term, this means NOTHING if Apple fixes it in the next couple of months. That's all there is to it. And the map software that comes out the other end is going to be more valuable to both Apple and iOS users than the Google Maps software that preceded it.