I can't believe this is something they're actually going to release. I hope that it might be better on release, but it seems like the backend should be continually upgraded.
That said, your example is pretty shocking considering Apple's historically stringent quality standards.
It this something that would have happened with Steve at the helm? I mean, the business case for moving off of your competitor's flagship map product is clear. You want to get them out of your product development cycle, you want to deny them revenue, you want to dilute their brand. I get that.
But still, Apple is ultimately achieving this by pushing what seems to be universally regarded as an inferior product out to its customers. It's basically a downgrade. When has Apple ever done that before?
Do you think Apple hasn't been working in this direction since before Steve left the helm?
Placebase acquisition: Jul 2009
Poly 9 acquisition: Jul 2010
C3 acquisition: Aug 2011
I mean obviously if it was a disaster they would have to go back and cut another deal with Google (or Nokia/MS) but it now becomes obvious why they held back turn by turn from the old Maps app for so long. Because you can legitimately argue that 6.0 Maps with some weak spots that can be improved over time but with turn by turn plus possibly Google Maps in the App store is better then 5.0 Maps powered by Google's superior data but without turn by turn.
As far as Google I'd guess they would have been fine to continue powering the default Maps app. Google's price might have gone up from 2007 but the quality increased by a similar amount.
I think the maps feature that Apple believed they could produce, at the time they made the decision, was probably very different from the maps feature they were actually able to produce.
iPhoto however, I think, could use some rethinking...
Now your are taken to some dead end Google MaP in the browser that does nothing.
WTH Apple?
Absent that, surely you see the problem with a maps.google.com link taking you to Apple's Maps app (no longer associated with Google in any way)?
Don't type: "21st and 6th", type "21st and 6th, CITY".
Apple Maps is a regression in certain areas (public transit, as noted above), and advances others (the turn-by-turn experience), so it's a mixed bag.
At the end of the day, most of these things are reconciled through the app ecosystem: if you are heavily dependent on public transit, Google and other app providers support you well. If you're a driver, Apple and TomTom provide worthy solutions. And so on with walking and biking directions. We, as consumer, get choices and it's relatively easy to switch between them.
That said, even if they do submit one immediately, I'm afraid Apple will tie it up in review for a month or two to allow their version to gain a userbase. I know if a Google version were available upon upgrade to iOS 6, I'd download it immediately. Transit directions are a must-have feature for me.
I hope you're not talking about the "fly around" view when turning a corner, because that is the most useless feature I've ever heard of for turn-by-turn navigation. NO ONE should be looking at their phone while making a turn.
Maps has a huge local revenue opportunity for Google. It has user intent, most of the searches are commercial, you know the user's tastes and hangouts (through past searches), and the user is addressable (since they are close to the item of interest). This means high CPC rates (or equivalent) if you can deliver a real ad product. Thus, I'd bet pretty strongly that a maps product will be coming to iOS since Google would hate to risk losing those valuable eyeballs.
http://www.nytimes.com/2012/03/20/technology/many-sites-char...
Google walked back some of the worst effects of the changes:
http://googlegeodevelopers.blogspot.ca/2012/06/lower-pricing...
but by then the damage had been done in terms of Apple's (and developers') perception of the Google API.
(for developers, AFAIK there has been no cost for using Map Kit in iOS or a MapView in Android)
You sound like those soccer moms I make house calls for who just think it's easier to throw away a working system and buy something else.
Normal situational example: I'm in a neighborhood, say Fort Greene, and I'm meeting a friend for dinner at a restaurant I've never heard of in the East Village. First, I need to be able to find that restaurant by searching for it in Maps -- this largely doesn't work anymore. I often get results that are totally incorrect.
But say I do find the location, I then need to figure out how to get there from a neighborhood I don't actively live in. Do I take the A train and transfer to the F and walk from the lower east side? Maybe it's faster to walk to the Q and get off at Union Square. Or maybe the manhattan bridge is under construction, and it actually would be faster to take the G to north Brooklyn and transfer to the L. This subway system is so massive that even native New Yorkers get turned around and need directions.
If you don't actively live in NYC I think it might be hard to realize how significant losing transit directions is, not to mention useful location search.
The same thing is happening here. A lot of people who live in big cities now depend on their phones for directions, and a lot of them need transit directions in addition to driving directions. A phone that can't do that has greatly diminished value. Not everyone wants a phone as a status symbol: some want it to actually do useful things.
And how many people have switched to Mac due to an inferior product feeling? Sure you can still use the computer but if one of the main purposes of having it doesn't work for your needs, why keep using it?
(irrelevant fact: Maps is the MOST important app on the iPhone for me - after the browser, of course. I've put my life on its "hands" an infinite number of times...)
I also need correct search results. For example, searching for "Flatbush Farm" -- a bar/restaurant near my apartment in Brooklyn -- yields the correct establishment on Flatbush and 6th, as evidenced by the Yelp reviews, but drops a pin in Queens. I've reported many incorrect listings over the past couple of months and none of them have changed.
I think this is why Apple's plan to relegate public transport directions to external apps might be a good idea: there's no way a single company -- even one the size of even Google! -- can keep track of all the minutiae involved in planning routes for every public transport system around the world, whereas app makers can. Even today, every public transit system that I've been on has one or more apps, so I doubt uptake will be a problem. And with the new APIs in iOS6, it should be much easier to get directions via external apps, since they show up in a list right in the Maps app.
Oh, and the app worked offline, which as you might know is mighty helpful in large parts of the subway. :)
Granted most excursions don't necessitate the public transit directions in the Bay Area, it was amazing to have while traveling to new cities.
The people for whom this is a big issue are a fairly small proportion of the global population. Basically those in the US who live in major cities and are users of the transit system. In San Diego and New York this is a big issue and those are centres of the HN readership and probably also the tech media which might be important but the practical impact of this limitation may be limited.
So while this looks like it will fill a gap on iOS, it's something I'm unwilling to wait for.
Apple is reporting heavy traffic only on Flatbush, Atlantic, and the BQE (major traffic arteries for those not familiar with Brooklyn).
Google is reporting what Apple has, plus traffic patterns on a lot of other local avenues (3rd, 4th, 5th, 7th, Vanderbilt, Fulton, Union St, etc).
Remember: When Steve Jobs was first defending the 30% app store cut he said something to the effect that it wouldn't matter in the long run because everybody was using web apps anyway.
Trying to take the subway to unfamiliar parts of the city forces me to use google maps in the browser. Addresses seem to be hit or miss -- I've often spent time searching for an establishment or address just to give up and use google maps in the browser.
I've basically had to revert to how I got around the city prior to having a smartphone -- use my computer and remember how I need to get there before I leave.
Apple Maps is potentially a huge fail for anyone living in a major city.