Owner: Finest in the district!
Customer: (annoyed) Explain the logic underlying that conclusion, please.
Owner: Well, it's so clean, sir!
Customer: It's certainly uncontaminated by cheese....
21–30 of 41 posts
Owner: Finest in the district!
Customer: (annoyed) Explain the logic underlying that conclusion, please.
Owner: Well, it's so clean, sir!
Customer: It's certainly uncontaminated by cheese....
For the umpteenth time: There was never a Google Maps app on the iPhone, there was an Apple app powered by Google's data . The correct way of stating this is that Apple's iOS6 maps app is more data efficient than previous versions. As for the main reason the current app is more efficient is that it relies on vector graphics instead of image tiles, a technique Google have been using on Android for nearly 2 years: http…
Calm down. Everyone is just calling it Google Maps out of simplicity. And yes it is vector on Android which was rumored to be one of the reasons Apple even started on this whole maps adventure. Because Google wasn't willing to license the vector data to give Android a competitive advantage.
Many in the press keep omitting the fact that Android did it first, which I think is important in this climate where Apple is very litigious regarding this stuff and the press keeps touting their originality while simultaneously dismissing other innovators.
Of course you use less data when you don't need to download anything important...like oh say, roads, important subway stations, or cities!
Yeah, I'd rather wait 5 minutes for correct information instead of waiting 2 minutes for incorrect information.
For the umpteenth time: There was never a Google Maps app on the iPhone, there was an Apple app powered by Google's data . The correct way of stating this is that Apple's iOS6 maps app is more data efficient than previous versions. As for the main reason the current app is more efficient is that it relies on vector graphics instead of image tiles, a technique Google have been using on Android for nearly 2 years: http…
Calm down. Everyone is just calling it Google Maps out of simplicity. And yes it is vector on Android which was rumored to be one of the reasons Apple even started on this whole maps adventure. Because Google wasn't willing to license the vector data to give Android a competitive advantage.
but after reading you point, as a laymen, I have no idea what to believe.
The title is a little misleading. It may be more efficient compared to the 5 years old Google Maps app on iOS, but Google Maps for Android has been vector based since December 16th, 2010, when they launched Google Maps 5.0. http://googlemobile.blogspot.com/2010/12/under-hood-of-googl... Also don't forget Apple's Maps retrieve a lot less data than Google Maps, since they don't actually have that data. Google Maps offe…
>Also don't forget Apple's Maps retrieve a lot less data than Google Maps, since they don't actually have that data. Google Maps offers a lot more information. Well this is just stupidity at its finest. A few extra POIs/streets would pale in comparison to the difference between vector and raster images.
Earlier quoted context omitted.
Calm down. Everyone is just calling it Google Maps out of simplicity. And yes it is vector on Android which was rumored to be one of the reasons Apple even started on this whole maps adventure. Because Google wasn't willing to license the vector data to give Android a competitive advantage.
I'm just a bit bothered by this phenomena of discovering features on the iPhone that were present on Android for ages and then attributing them to Apple: the notifications shade, voice input, voice actions, the ability to answer phone calls with canned texts, and now maps among many other things. Many in the press keep omitting the fact that Android did it first, which I think is important in this climate where Apple…
For the umpteenth time: There was never a Google Maps app on the iPhone, there was an Apple app powered by Google's data . The correct way of stating this is that Apple's iOS6 maps app is more data efficient than previous versions. As for the main reason the current app is more efficient is that it relies on vector graphics instead of image tiles, a technique Google have been using on Android for nearly 2 years: http…
Calm down. Everyone is just calling it Google Maps out of simplicity. And yes it is vector on Android which was rumored to be one of the reasons Apple even started on this whole maps adventure. Because Google wasn't willing to license the vector data to give Android a competitive advantage.
He is calm and pointing out a fact.
>Everyone is just calling it Google Maps out of simplicity.
No they aren't calling it Google Maps out of simplicity. Read the article:
"Apple Maps has been getting its share of negative attention since being released, but some new research shines a bright spot on the comparison between Apple’s and Google’s mapping apps."
"Results for the satellite view in Maps showed Apple’s app used about half of Google’s mapping application."
Earlier quoted context omitted.
I'm just a bit bothered by this phenomena of discovering features on the iPhone that were present on Android for ages and then attributing them to Apple: the notifications shade, voice input, voice actions, the ability to answer phone calls with canned texts, and now maps among many other things. Many in the press keep omitting the fact that Android did it first, which I think is important in this climate where Apple…
No one really claims that Apple did them first. In some cases, these features have gained press just because Apple's solution was more elegantly designed.
Also it could be because Apple feels the need to give every minute feature a name which is also a PR thing.
Oh, and none of the features I've mentioned are better executed on iOS.
Earlier quoted context omitted.
The title isn't misleading because the test has nothing to do with Android. They're comparing the two iOS map offerings, not cross-platform.
How would you infer that from the title? Bandwidth used by apps can and is frequently constant across platforms. Won't adding a "on iOS" at the end help clarify things?