• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

PSA: new Apple Maps

Page 4 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
The difference is that Apple markets the user experience. It's supposed to just work. They promise that on stage when they're doing the slideshow of the shiny new device and its capabilities. Google does no such thing and has no such reputation. You pay a premium for the Apple device, and you expect a premium experience - they missed the mark this time. Will it matter? Probably not.

I'm not a fan or hater of either Google or Apple. I own both Android and iOS/OSX devices, and in some way, am long both their stocks.

In what way does Apple's Maps "miss the mark?" Admittedly, I haven't used it much so far. The only thing I miss is Street View. It has far fewer database problems than Google Maps at this point (but I'm sure there will be more as the database grows). I still haven't encountered a problem and most of the "problems" people listed are intended behavior and *identical* to Google's implementation.
 
You're like that monkey that will not let go of that shiny bauble.

Let me explain it to you, sorry I left my finger puppets at home. If you know anything about developing software or apps, you probably know that the first and most important rule is to make sure the product work as intended, like someone said, the user experience. If I search for London and I'm sitting in the middle of America, how does the software know what I'm looking for exactly?

My kid likes to type in random places in Maps to learn where they are, a sort of educational tool, so giving wrong or limited geographical data will confuse the end user. The simplest solution to give multiple results and asking which London you're looking for.

But you're too fucking stupid to realize that the software is incomplete and sloppy. That or you're one of those jackass apple fanboys.
Well, it's best that the kid learns that sometimes he needs to be specific. There are lots of cities that don't have unique names.
 
In what way does Apple's Maps "miss the mark?" Admittedly, I haven't used it much so far. The only thing I miss is Street View. It has far fewer database problems than Google Maps at this point (but I'm sure there will be more as the database grows). I still haven't encountered a problem and most of the "problems" people listed are intended behavior and *identical* to Google's implementation.

Not personally sure, but their customers are complaining about it, and that means Apple missed the mark. Apple's strategy is entirely different than Google's. Their products can behave exactly the same, and one can be acceptable while the other is not, because their customer acquisition strategies are entirely different.
 
It's almost like Apple is in the same position that Microsoft is with their entire smartphone OS. Essentially, Apple came in late in the game with a map app. Google built up Streetview over the course of years. I do use streetview to see what my destinations look like (sometimes), and it's a bummer that it's gone. However, I'm not clamoring over it too much. I'm sure I'll survive, and plus... I normally do most of that destination surveying on a computer anyway. It involves a hell of a lot of moving around, which would be a pain on any smartphone (I even streetview turns to see if there's anything funky about them).
 
In what way does Apple's Maps "miss the mark?" Admittedly, I haven't used it much so far. The only thing I miss is Street View. It has far fewer database problems than Google Maps at this point (but I'm sure there will be more as the database grows). I still haven't encountered a problem and most of the "problems" people listed are intended behavior and *identical* to Google's implementation.

No public transit data at all.
 
Back
Top