I don't see this an Apple bashing thread. It's the truth, they have some major issues with their maps. What's so bad about being realistic about it? For the image the company likes to project, it was a fiasco.
I don't see this an Apple bashing thread. It's the truth, they have some major issues with their maps. What's so bad about being realistic about it? For the image the company likes to project, it was a fiasco.
Apple forgot an important rule when dealing with third-party data:
Trust, but verify.
This kind of thing should have been going on long before the Apple Maps app ever shipped.
Bingo. We need a crusade to get Cook FIRED. They have so much money they don't know how to spend / invest it for the Apple Ecosystem but they can't get a current featured Mac Pro out and they are just now hiring a mapping team![]()
Dunno where you live, but it always works for me. I just don't use it much because there's no voice navigation on the Maps app for iPhone 4![]()
I've been trying to give them free "ground truth" info for Australia via the in-built reporting tool since Maps was in beta.
So far, none of the corrections have made it into the maps. They are as woefully inaccurate as on day one.
By not releasing it until it was actually ready?
If Google pulled all of their apps from the iPhone (as Apple tried with maps) then the iPhone wouldn't be near as useful
If by ready you mean 100% accurate then it would never be released.
That it was released at the level that it was is partly due to the vastness of change and the need for user imput so they can have something in the next decade. And partly due to a certain ego that likely said it was ready when it wasn't. Apple has this nasty habit of trusting SVPs etc when they say things, same with partners. They found out the hard way that this time that was a bad move and they got half ass data and an iOS full of serious bugs. And it's possible that that same ego was in charge of data oversight which might be why Cook demanded he apologize to the users as well. When Forstall didn't, out he went. Bad enough he was an ass that wouldn't listen to anyone but Steve and didn't play with others, failing the customers on a huge level was the end.
Tim vowed to work on the issue and it has happened. These are managers, who knows how many staff are already in place and doing work. Major updates have happened in some areas and the rest will come. Not even Google was perfect for the like the first 5 years. Heck it still is only perhaps 95% there (if you don't include their driving instructions which are more like 70% there)
unfulfilled introductions (Apple TV, China Mobile, Aperture X, etc.)
IMO, Apple should have done a bit more quality control before they released it.
Who do you think was in charge of iOS QC. Scott Forstall. The same ego jerk that wasted time on cute moving shadows on faux knobs while missing a serious wifi bug. Same guy that refused to apologize for Maps, an act he was likely asked to do because he was in charge of the software and making sure everything was in order by launch.
Pretty much every location you search.
For example, go here:
10817 Northwest Ambassador Drive, Kansas City, United States
You can't even read 'speed limit' on the 'speed limit 35' sign. And the number '35' is questionable. Only because I know it's a number, I know what it is. The no parking sign below it is bad, the sign across from the speed limit sign is unreadable.
That's just one I found in my first random search. I typed in 'Kansas City, MO' and moved north about 100 yards.
- Did you pay something for Apple Maps?
- Has using Apple Maps harmed you in some way?
- Did Apple make some guarantee about Apple Maps?
- Did Apple prevent you from using Google Maps or other alternatives?
If the answer to each of the above questions is "no", then yes, you are whining. What *exactly* is it that you think you are entitled to?
Curious. Where is this place with the signs were completely blurry and shadowed?
Awesome. I'd rather incomplete maps than inaccurate maps. Maybe this will fix both!
They still have inaccuracies and mistakes, and they've even been driving camera cars around for years. Now that's embarrassing.
Well, how does it compare to the picture in Apple Maps? Exactly, no competition. Apple Maps is a competitor to Google Maps only in nagromme's (and some other super Apple fans) World.
Dunno where you live, but it always works for me. I just don't use it much because there's no voice navigation on the Maps app for iPhone 4![]()
Well said.
I think Apple needs to do a lot more than hire a few more people in order to get to Google's mapping level.
Yes, let's fire Cook because of the Mac Pro. The world of 2013 is eagerly awaiting a huge, stationary desktop tower. Apple isn't innovating in this space, which is why Dell is... or is it HP... wait is HP even in business anymore? Is it Compaq? Could you remind me which company is building that amazing tower that everyone wants and is doing billions and billions in annual revenue??
Those are all rumors, nothing more, at this point. So given that there's zero proven truth to any of them, they are hardly 'unfulfilled' anything.
That you would see them that way just shows that you are the type to believe what you read no matter the 'unnamed sources', like many of the folks that listen to pulled it from a lower orifice speaking analysts.
It shows nothing of the kind - go back and review the total picture - as the last article postulated, Cook is becoming Apple's Steve Balmer due to his performance.
This weekend, for the very first time* since the Maps switch, I actually had a need to go back to the Google app.
I wanted to use Street View to see the signs on buildings and find the right one.
Unfortunately....
a) Street View was completely blurry and shadowed and even enormous signs were unreadable on storefronts.
b) Google had the location completely wrong.
c) Compounded by the fact that getting around (reaching the CORRECT location manually) in Street View is an incredible pain compared to smoothly zipping around in Flyover. (Which, granted, puts you 50 feet in the air at best, but is still a great, immediately recognizable view of street in high detail. You can zoom in quite far in Flyover, and even read larger commercial signs.)
So I went back to Apple Maps and followed the route. Lo and behold, Apple has the location exactly right. The pin was in front of the exact building, and I didn't need a sign after all.
Some people have problems with Apple Maps, no doubt. We forget how often Google Maps has problems too.
* I do use Google for transit... but I do my destination search in Apple Maps because it has been easier and equally accurate. Then I hit the Transit button in Apple Maps which hands the query off to the Google app. Very painless: I get Google's transit results without having to deal with Google's painful searching... such as a failing to access my Address Book and Home locations, and failing to remember a search I just made 10 seconds ago! It's too bad, because Google IS the best at getting a badly-typed query right: I give full credit there.
Well said. It is just seems easier to bash Apple and forget that Google has the same issues.
Most people who make that claim, like the Apple maps app / interface better. Very few people are claiming that the Apple data is better than the Google data. In any case, you don't just finish the mapping data then stop. Maps are always changing.
I thought that people expected more refinement from Apple than they do from it's competitors?
Too lazy to find sources but from what I've read on this type of technology(might have been a TED talk), this sort of thing isn't that far away at all. The only thing I see being a setback is regional governments permitting it. From what I remember Nevada was going to be or is the only state so far to allow it.
Your reading skills must be a bit limited - the Mac Pro example is but one small example that I cited - it is the whole picture that needs to be looked at.
40% loss of stock value,
maps introduction,
using your biggest competitor for sourcing screens and chips.
on and on.