Live data from Hacker News

If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

techcrunch.com

11–20 of 109 posts

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#11
The lack of including public transit routing was a huge miss -- the "Designed in California", everyone has a car confused the decision making.

I've found the Embark transit applications to be a great alternative (at least for Chicago). It doesn't make up for other missing features like Street View, but you'd be surprised how many users did not even know those features existed.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#12
Really? Although the maps show less information, I found the navigation feature much more usable now. For me, it's the most useful feature since I don't have a car with GPS and TomTom's app is pricey. Now I have it built-in.

For finding other stuff I can always use other apps or Google Maps mobile, which is very decent too.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#13

This is exactly the OPPOSITE of why I'm intrigued and impressed by Google as a company. They just want people to have access to their services. They are not about authoritative control over who gets access and locking their users in a walled garden. Android is wonderful and Google's done a great job of integrating their services with it.. but why shouldn't iOS users have at least some of the same benefits (if Apple a…

Well, it is likely that some deal-making (or lack thereof) behind the curtain is why Apple had to release a new maps tool in the first place.

But for users, yes.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#14

My bet is that the end users aren't even going to notice. I switched my website maps from Google to OSM/Leaflet and absolutely no one noticed or cared enough to email me about it. Disclaimer: I didn't use OSM's default/ugly color palette. Disclaimer #2: I have used iOS 6 maps, and the most visible change (other than the color palette) is that subway markers are clickable and that Yelp is more tightly integrated into…

Changing the maps you use on your web site and changing the maps on a person's smartphone are hugely different.

Without knowing more about your web site I can't do a detailed comparison, but unless people use your web site every day, on the move, to search for transit, business and social locations then the use cases just aren't the same. Not to mention that the biggest issue with Apple Maps is the dismal coverage outside of the US.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#15
I am surprised Samsung didn't pounce on this opportunity in their marketing materials.

Instead they are propping features like "Palm Picture Capture", "Tilt to Mute", and other dumb things that nobody really cares about. http://images.latinospost.com/data/images/full/5424/samsung-...

Things like this is what differentiates great companies, from ones that just doen't get it. Users don't care about useless feature list, they care about end experience.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#16
post #6

The iOS 6 maps subsystem is the worst OS component regression Apple has shipped since Open Transport 1.0. It is really bad, and if navigating a city is one of your key phone usage scenarios, this change makes Apple's arch-rival's devices significantly more attractive than they otherwise would be. I carry around both the latest Apple phone and the latest Google phone, and this is one area where the Google phone was al…

I think it's a tricky question.

Wait six months: increases the pain iOS users feel, and possibly increases migration to Android, but by how much? If you've bought an iPhone 5, in many cases that means a 1-year contract (or renewal). And in six months, Apple may have released a better Maps app that fixes the problem.

Release Google Maps for iOS sooner: iPhone users feel less pain, but Google Maps keeps more users.

Actually though, the more I think of it, even in the latter scenario, Apple still wins, because whenever they release their fixed Maps app, they win back the entire market because they own the platform. So maybe the first strategy actually makes more sense.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#17

heh. Google can't release a Maps app - mostly because that would be duplicating a service that Apple already provides, and apple hates competition !

Google has made several apps that duplicate functionality (Gmail, Chrome, etc.) Apple doesn't care.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#18

This is exactly the OPPOSITE of why I'm intrigued and impressed by Google as a company. They just want people to have access to their services. They are not about authoritative control over who gets access and locking their users in a walled garden. Android is wonderful and Google's done a great job of integrating their services with it.. but why shouldn't iOS users have at least some of the same benefits (if Apple a…

  > They just want people to have access to their services.
They just want to have access to the people :)

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#19
post #11

The lack of including public transit routing was a huge miss -- the "Designed in California", everyone has a car confused the decision making. I've found the Embark transit applications to be a great alternative (at least for Chicago). It doesn't make up for other missing features like Street View, but you'd be surprised how many users did not even know those features existed.

SF & NYC are the two most transit heavy cities in the USA. Cupertino is a 1 hr drive from SF, and I bet many apple employees live in SF. I'm fairly sure this was just a cut feature for the time they have and they probably already have it working or are developing it for iOS 7.

Re: If I Were Google, I Wouldn’t Release A Native iOS 6 Maps App For Six Months

#20

heh. Google can't release a Maps app - mostly because that would be duplicating a service that Apple already provides, and apple hates competition !

This was more true in 2008-2010 maybe, but recently Apple has been much less restrictive. There are 3rd party browsers (chrome, opera, Firefox)*, 3rd party mail apps(gmail, Firefox), and 3rd part maps apps (tomtom).

That said, the lack of third party transit from apple is pretty horrible, and the API for the maps app is pretty limited (you have to throw the start and end points to your app, there's no overlays or anything like that)

Post reply on HN