#google maps

Ladies and gentleman, I present to you 3,000 words in which Danny Sullivan talks himself into something, then talks himself out of it, then back into it.

Seriously, why does Google Maps not work on your Windows Phone? I don’t know, why doesn’t it work on your graphing calculator or your espresso machine?

It’s simple really. Google made sure Maps worked on Windows Mobile because it had market share. Google doesn’t give a shit about Maps working on Windows Phone because it doesn’t. Any questions? Consult Sullivan’s post and then come back here again.

publishforlove asked:

What are your thoughts on the new google map app for iPhone?

It’s great. I’ve been using it all morning to get around. It’s worth it for the clearly superior place search functionality alone.

Judging from my inbox/replies/etc, it seems like a lot of folks expect me to take a shit on the app. I’m not going to do that. As I’ve always said, my only requirement to use something is that it be the best. And that’s clearly the case here.

Google Maps is superior to Apple Maps in most (though not quite all) ways. And I’m excited to have it back on the iPhone. I’ll be using it constantly.

John Gruber:

Everyone else in the tech world expected Apple to release its own mapping service for three years, but Google, the one company that stood to lose the most, did not? OK, sure. If you believe that, I have a melted bridge to sell you.

I’m not sure what Google’s play is here in strategically leaking some of this info. Do they want us to feel bad for them? Inspire more outrage against Apple for the Maps situation? The way these stories are set up, the opposite is almost true. They makes it seem like Google is kind of clueless (which I don’t think is actually true).

Or maybe they just felt the need to temper expectations for a Google Maps iOS client, since it’s not coming anytime soon (despite erroneous reports suggesting it was already submitted and Apple was blocking it).

Since we’re just about week into regular, everyday usage of Apple Maps with iOS 6, I started this Branch to get some impressions beyond the hyperbolic headlines. And guess what? People are actually posting well-reasoned, thoughtful, and balanced insights into the feature. Yes, this is actually taking place on the internet!

Great read by Alexis Madrigal on how Google got so far ahead in maps — and why they’re likely to stay ahead.

There are a number of factors at play, but one key that stands out are the Street View cars. If Apple is going to compete in the space, they’re going to need some answer not to the Street View product, but to the data those cars send back. (Which is undoubtedly why we’re seeing Apple quietly partner with companies like Waze.)

brad-t asked:

To be fair, the fact that iOS6 maps doesn't have public transit really, REALLY sucks. I'm sure I'm not the only person who uses Google Maps primarily for transit directions.

It does, I agree. I’m interested to see how they integrate the third-party apps to do this. 

Still, I suspect Apple will address this with their own solution sooner rather than later.

Read: Please, please, please don’t switch to an iPhone in a few weeks with their new iOS 6 maps. They have no transit! We’re doubling down on transit. Hell, we’re tripling down on it. We’re going to pour every resource we have as a company in to transit. Transit. Transit. Transit. Transit.

Google Maps Product Manager Thor Mitchell:

As you may know, last year we introduced limits on the number of free maps that developers could show daily through the Google Maps API. Since then, we’ve been listening carefully to feedback, and today we’re happy to announce that we’re lowering API usage fees and simplifying limits for both Styled and regular maps.

"Since then" — let’s be clear, that happened in October of last year. In the eight months since then, what has changed? Not much beyond a little company called Apple entering the space.

I’ve talked to a lot of developers over the past several months — not one of them can understand why Google made these changes in the first place. It led big startups like Foursquare to abandon Google Maps on the web. Even with the high rates, it can’t be a huge amount of money for Google relative to their overall revenues.

But still, they did not make this change until after Apple maps were unveiled. And they didn’t just cut prices, they slashed them by 8x. 8x!

Can’t imagine why.

Update: One reason for the price change initially was apparently spam. As in, Google thought that by charging sites for heavy usage, they’d cut back on the “Live Nude Girls in Houston!!!” embedded map ads. Still, it’s not clear how they couldn’t see the downside for big *real* partners.