iOS 6 maps

My good friend Dom has written an interesting post regarding his frustrations with Apple's hardware due to the lack of upgradability.

Several days after updating my iPhone to iOS 6 I'm still smarting over how Apple thought they could get away with releasing such an indefensibly poor excuse for a maps app.

It's quite honestly the most error-strewn piece of crap I've ever had the misfortune to use. That it was cynically deemed suitable to let loose on the public by Apple is what I find the most disappointing though.

Take a look at the screenshot of the East Sussex coastline above...

Can you believe that only Alfriston is labelled correctly; all the other location names are in the wrong places.

Falmer should actually be labelled Woodingdean (Falmer is further north).
Rottingdean should be labelled Saltdean (Rottingdean is slightly to the west).
Newhaven should be labelled Peacehaven (Newhaven is to the east).
Bishopstone should be labelled Seaford (Bishopstone is further to the north-west).

Unbelievably bad.

This is just the tip of an enormous iceberg, though. There are tons more examples here: The Amazing iOS 6 Maps

Now check out Apple's maps icon shown here on the left.

Notice how the turn-by-turn navigation route (in blue) suggests you can take a left turn from the bridge over the freeway (white) onto the freeway itself (yellow).

What hope is there for iOS 6's maps app when even the icon is so wrong...?

UPDATE: As Dom says in reply to my comment on his blog post, it's not that the app itself is at fault, more the data is bad. Of course, he's right. Apple will fix this, but it will take some time.