How were they playing catchup if they already had the technology. Choosing when to release it on a platform because of business decisions isn't the definition of catching up.
I think your a little confused. We are comparing the iOS version of google maps to Apple Maps, not android and iOS. If Apple release a new version of iTunes with new features for the Mac and then some time later release an updated version for windows with those same features it would be correct to state that the features in the windows version have now caught up with the Mac version.
You can not simply make up your own definition for a phrase or change the parameters of a discussion because you don't like being wrong.
Google was neglecting to release features for the iOS version of their maps app. Not until after Apple Maps came out did they implement those features in their iOS version.
Apple still have areas they need to catch up to google maps such as business searches however they are moving at a much faster rate than google in that area given the head start of several years that Google has in that area.
This is reminiscent of PC programs ported to Macs bringing some Windoze interface elements. It was ugly and I never liked it. With Apple's much tighter control over iOS, I hope they won't allow Google's UI to ruin iOS users experience.
Google Maps is great. In my area, it has far more POI data that Apple Maps. Also, turn-by-turn directions available on my iPhone 4. Once I upgrade to 6+ in the coming weeks (provided it is ever in stock at my carrier) I'll give Apple Maps another shot but I'm guessing the POI data will keep me on Google Maps. Just my opinion.
Same here. I use it because Apple Maps doesn't support turn by turn directions. I also like street view in Google Maps.
You can not simply make up your own definition for a phrase or change the parameters of a discussion because you don't like being wrong.
Google was neglecting to release features for the iOS version of their maps app. .
You mean like exactly what you did?
Google didn't release vector maps on iOS because they were trying to force apples hand. They released it a couple of months after Apple came out with their maps. You think google developed the app in 8 weeks?
Here's how it went.
Google : we'll give android users nice vector maps and not ios until Apple cave in and accept our mapping solution.
Apple : let's hobble together our own map solution and screw Google.
Google: oh Apple made their own maps let's show them how much better ours is.
Google release vector version a few months later.
The fact that google didn't release a version of their maps app with vector images on the iPhone until after Apple did exactly my point. On iOS they were playing catch-up to Apple Maps. The fact that they already had vector maps on android but took over 2 years to bring it to iOS shows that they were unnecessarily playing catch-up with that feature.
And I never said that street view and flyover are the same thing. In fact I never said google had even caught up with Apple on that feature. But in response to your comment I'm not sure how street view and flyover are "Completely Different". Sure they are definitely different features but they do have similarities. Back before Apple Maps I would use street view to get an idea of what an area looked like, which is exactly what I use flyover for. It's just that I find flyover more enjoyable to use but to each their own.
Except that you're forgetting that the maps app wasn't Google's map, it was a app made by Apple using Google's map data. Only when Apple went elsewhere for their data did Google make a Google maps app for iOS.
It really depends on what features you need from your maps app as each of these has strengths in certain areas. Overall I would say that they are fairly even when looking at the strengths and weaknesses of both products.
The main selling point for me with Apple Maps though is privacy and iOS integration. I still used google a few times after Apple Maps rolled out but have been using Apple Maps exclusively for a while now and have had no issues with finding business or using turn by turn navigation. I did have one issue with getting directions a couple of months ago where Maps wanted me to take a route that was not very direct and didn't give me a better option. Put it into google and got the same result.
Apple has been in the maps business for a much shorter time than google but it's google that have had to reinvent their product to play catch up to Apple with things like vector maps and flyover. The continuity features of being able to look up directions on my Mac and then easily load them on my iPhone for directions are also a selling point for me.
I don't see google ever getting back to the days of having a majority share of iOS users having Google Maps on their iPhones. I expect over time as Apple adds integrated features to their Maps App that google can't compete with we will see less and less iOS users installing google maps.
Both have weaknesses and strenghts indeed. In Western Europe the poi data still isn't on par with Google Maps, some basic town information like the municipality a certain town is in sometimes also is wrong. It will find it just fine but somehow it's listed wrongly. But it's definitely improving and with time it will get there.
I just wanted to address something from your post, with fly-over it is possible that Google started developing its 3d imaging technology when Apple bought C3 Technologies. But I imagine something like that takes time and both were ready for release around the same time. But that's up for discussion, with vector maps you're wrong though. Google Maps for Android has had vector based maps since version 5.0 released in 2010. http://googlemobile.blogspot.com.au/2010/12/under-hood-of-google-maps-50-for.html?m=1
Both have weaknesses and strenghts indeed. In Western Europe the poi data still isn't on par with Google Maps, some basic town information like the municipality a certain town is in sometimes also is wrong. It will find it just fine but somehow it's listed wrongly. But it's definitely improving and with time it will get there.
I just wanted to address something from your post, with fly-over it is possible that Google started developing its 3d imaging technology when Apple bought C3 Technologies. But I imagine something like that takes time and both were ready for release around the same time. But that's up for discussion, with vector maps you're wrong though. Google Maps for Android has had vector based maps since version 5.0 released in 2010. http://googlemobile.blogspot.com.au/2010/12/under-hood-of-google-maps-50-for.html?m=1
Guess you didn't get a chance to read my earlier posts. With vector maps I'm not wrong as I had already stated that google had that on their android app. But the fact they had it on their android app is irrelevant to iOS users.
But your right about 3d imagining technology taking time to develop before release and the fact that both google and Apple's maps apps having strengths and weaknesses.
Except that you're forgetting that the maps app wasn't Google's map, it was a app made by Apple using Google's map data. Only when Apple went elsewhere for their data did Google make a Google maps app for iOS.
How am I forgetting that? I've never said that wasn't the case.
How am I forgetting that? I've never said that wasn't the case.:\
The maps app wasn't Google's until after the agreement ended, and Apple made their own app. It was only then that Google was allowed to make a maps app for iOS.
Nice comeback. Not sure what you even mean by that though...
Quote:
Originally Posted by patpatpat
Google didn't release vector maps on iOS because they were trying to force apples hand. They released it a couple of months after Apple came out with their maps. You think google developed the app in 8 weeks?
Care to explain what google was trying to force Apple's hand about or will it just be further speculation without evidence? Apple was already working with google to utilise google's maps data in their maps app. What else do you think google wanted? or are you trying to say google was trying to force Apple not to use google's map data? A more feasible speculation would be that google wanted to withhold features from the iOS version to make android more appealing but of course that is just speculation also. And why would anyone think it would only take 8 weeks to develop the app? google knew earlier than 8 weeks in advance about the change but who's to say they weren't working on their own iOS version even before they knew Apple would be ditching them.
Quote:
Originally Posted by patpatpat
Here's how it went.
Google : we'll give android users nice vector maps and not ios until Apple cave in and accept our mapping solution.
Apple : let's hobble together our own map solution and screw Google.
Google: oh Apple made their own maps let's show them how much better ours is.
Google release vector version a few months later.
Sorry, didn't realise patpatpat was your alias Eric Schmidt. Good to know you have so much inside information about exactly how it all went down. /s
So earlier you said that google would have spent more than 8 weeks creating their iOS maps app and accused me of thinking they rushed it out in 8 weeks despite the fact I said nothing to imply that. Now you are telling me exactly how it went down and that google did rush together their maps app after Apple released their updated maps app that didn't use google's data. You're obviously so desperate to defend google that you're not even thinking about what your typing...
Quote:
Originally Posted by patpatpat
That's not catchup by anyone's definition.
Yes it is.
Reading through your previous posts on other threads has been very entertaining also. You claim to use a variety of devices from different manufacturers including Apple and yet you have nothing to say about Apple apart from the issues you've had. Are you just searching through Apple's support pages to find problems you can talk about?
You have a lot of very positive things to say about google however, most of which are accurate. As I stated in the beginning I feel both Apple and google's maps apps have their strengths and weaknesses. Not sure why you decided you needed to try and prove that wrong but you've been doing a lousy job so far.
The maps app wasn't Google's until after the agreement ended, and Apple made their own app. It was only then that Google was allowed to make a maps app for iOS.
The Google Maps app for mobile devices rolled out vector-based maps beginning in 2010. There's never been a Google Maps app for iOS that wasn't vector AFAIK. I believe that's the point he was attempting to make.
The Google Maps app for mobile devices rolled out vector-based maps beginning in 2010. There's never been a Google Maps app for iOS that wasn't vector AFAIK. I believe that's the point he was attempting to make.
Your correct. There hasn't been a a google maps app for iOS that wasn't vector based.
Nice comeback. Not sure what you even mean by that though...
Yes it is.
Reading through your previous posts on other threads has been very entertaining also. You claim to use a variety of devices from different manufacturers including Apple and yet you have nothing to say about Apple apart from the issues you've had. Are you just searching through Apple's support pages to find problems you can talk about?
You have a lot of very positive things to say about google however, most of which are accurate. As I stated in the beginning I feel both Apple and google's maps apps have their strengths and weaknesses. Not sure why you decided you needed to try and prove that wrong but you've been doing a lousy job so far.
Did I forget to mention I'm holding a lot of AAPL stock?
Comments
I think your a little confused. We are comparing the iOS version of google maps to Apple Maps, not android and iOS. If Apple release a new version of iTunes with new features for the Mac and then some time later release an updated version for windows with those same features it would be correct to state that the features in the windows version have now caught up with the Mac version.
You can not simply make up your own definition for a phrase or change the parameters of a discussion because you don't like being wrong.
Google was neglecting to release features for the iOS version of their maps app. Not until after Apple Maps came out did they implement those features in their iOS version.
Apple still have areas they need to catch up to google maps such as business searches however they are moving at a much faster rate than google in that area given the head start of several years that Google has in that area.
Same here. I use it because Apple Maps doesn't support turn by turn directions. I also like street view in Google Maps.
Google didn't release vector maps on iOS because they were trying to force apples hand. They released it a couple of months after Apple came out with their maps. You think google developed the app in 8 weeks?
Here's how it went.
Google : we'll give android users nice vector maps and not ios until Apple cave in and accept our mapping solution.
Apple : let's hobble together our own map solution and screw Google.
Google: oh Apple made their own maps let's show them how much better ours is.
Google release vector version a few months later.
That's not catchup by anyone's definition.
Except that you're forgetting that the maps app wasn't Google's map, it was a app made by Apple using Google's map data. Only when Apple went elsewhere for their data did Google make a Google maps app for iOS.
Both have weaknesses and strenghts indeed. In Western Europe the poi data still isn't on par with Google Maps, some basic town information like the municipality a certain town is in sometimes also is wrong. It will find it just fine but somehow it's listed wrongly. But it's definitely improving and with time it will get there.
I just wanted to address something from your post, with fly-over it is possible that Google started developing its 3d imaging technology when Apple bought C3 Technologies. But I imagine something like that takes time and both were ready for release around the same time. But that's up for discussion, with vector maps you're wrong though. Google Maps for Android has had vector based maps since version 5.0 released in 2010. http://googlemobile.blogspot.com.au/2010/12/under-hood-of-google-maps-50-for.html?m=1
Both have weaknesses and strenghts indeed. In Western Europe the poi data still isn't on par with Google Maps, some basic town information like the municipality a certain town is in sometimes also is wrong. It will find it just fine but somehow it's listed wrongly. But it's definitely improving and with time it will get there.
I just wanted to address something from your post, with fly-over it is possible that Google started developing its 3d imaging technology when Apple bought C3 Technologies. But I imagine something like that takes time and both were ready for release around the same time. But that's up for discussion, with vector maps you're wrong though. Google Maps for Android has had vector based maps since version 5.0 released in 2010. http://googlemobile.blogspot.com.au/2010/12/under-hood-of-google-maps-50-for.html?m=1
Guess you didn't get a chance to read my earlier posts. With vector maps I'm not wrong as I had already stated that google had that on their android app. But the fact they had it on their android app is irrelevant to iOS users.
But your right about 3d imagining technology taking time to develop before release and the fact that both google and Apple's maps apps having strengths and weaknesses.
Except that you're forgetting that the maps app wasn't Google's map, it was a app made by Apple using Google's map data. Only when Apple went elsewhere for their data did Google make a Google maps app for iOS.
How am I forgetting that? I've never said that wasn't the case.
The maps app wasn't Google's until after the agreement ended, and Apple made their own app. It was only then that Google was allowed to make a maps app for iOS.
You mean like exactly what you did?
Nice comeback. Not sure what you even mean by that though...
Google didn't release vector maps on iOS because they were trying to force apples hand. They released it a couple of months after Apple came out with their maps. You think google developed the app in 8 weeks?
Here's how it went.
Google : we'll give android users nice vector maps and not ios until Apple cave in and accept our mapping solution.
Apple : let's hobble together our own map solution and screw Google.
Google: oh Apple made their own maps let's show them how much better ours is.
Google release vector version a few months later.
Quote:
That's not catchup by anyone's definition.
Yes it is.
Reading through your previous posts on other threads has been very entertaining also. You claim to use a variety of devices from different manufacturers including Apple and yet you have nothing to say about Apple apart from the issues you've had. Are you just searching through Apple's support pages to find problems you can talk about?
You have a lot of very positive things to say about google however, most of which are accurate. As I stated in the beginning I feel both Apple and google's maps apps have their strengths and weaknesses. Not sure why you decided you needed to try and prove that wrong but you've been doing a lousy job so far.
The maps app wasn't Google's until after the agreement ended, and Apple made their own app. It was only then that Google was allowed to make a maps app for iOS.
Yes I know. Your point being?
Obviously I misunderstood your point, and we're in agreement. Apologies.
Obviously I misunderstood your point, and we're in agreement. Apologies.
No problem.
The Google Maps app for mobile devices rolled out vector-based maps beginning in 2010. There's never been a Google Maps app for iOS that wasn't vector AFAIK. I believe that's the point he was attempting to make.
Your correct. There hasn't been a a google maps app for iOS that wasn't vector based.
I was attempting to explain what his point probably was in a more concise way.
I already knew I was correct.
I was attempting to explain what his point probably was in a more concise way.
Cool. Thanks.
Did I forget to mention I'm holding a lot of AAPL stock?
Well that would be a good investment choice. But stock investment doesn't have to be based on what you personally think about a companies products.