Apple Partners With Parkopedia to Bring In-Depth Parking Data to Apple Maps

Jeez.. I thought it said Poképedia.... Time to delete this thing >.<

The only advantage that Google maps has, from a UI standpoint, is I like how the little blip on a map also shows the direction the phone is pointed in, presumably using the compass.

Wait, doesn't Apple Maps do the same thing?

'2012 : Google Maps >> Apple Maps... Apple spent 4 years to improve Apple Maps...
'2016 : Google Maps >>>> Apple Maps...

I actually think Google Maps has gotten worse and worse lately. It's way too bloated. The app used to launch instantly, now it shows a blank screen too long at first load. The slide-out menu from the left is very unintuitive. Google seems to be more interested in showing me ads than what I am actually looking for.

The only advantage that Google maps has, from a UI standpoint, is I like how the little blip on a map also shows the direction the phone is pointed in, presumably using the compass. Once Apple implements the same thing, I see no reason to keep the Google maps app.

Any improvement to Apple Maps is appreciated :)

'2012 : Google Maps >> Apple Maps... Apple spent 4 years to improve Apple Maps...
'2016 : Google Maps >>>> Apple Maps...

Google Maps is eight years older...

I actually think Google Maps has gotten worse and worse lately. It's way too bloated. The app used to launch instantly, now it shows a blank screen too long at first load. The slide-out menu from the left is very unintuitive. Google seems to be more interested in showing me ads than what I am actually looking for.

The only advantage that Google maps has, from a UI standpoint, is I like how the little blip on a map also shows the direction the phone is pointed in, presumably using the compass. Once Apple implements the same thing, I see no reason to keep the Google maps app.

I find Apple Maps more attractive and easier to use than Google Maps, but GMaps has certain advantages that are undeniable, for example:
- search along the route (eg, for gas stations, food, or lodgings, while in nav mode, and ON the already programmed route)
- display of useful information for some searches (eg price at gas stations, price for lodgings). These may not be perfectly accurate, but they allow you to rapidly scan eg the expensive hotels from the cheaper ones
- pretty much everything related to search (including "unusual" searches like "where do locals eat")
- much more willingness to utilize crowd-sourcing for all sorts of purposes including things like allowing users to easily and rapidly rate establishments and determine favorites. Apple's obsession with privacy is (IMHO) preventing them from handling a number of use cases that they could, at worst, just allow people to opt into.

- Google has a mechanism (lousy and painful, but at least it is there) for establishing way points along the way (eg I want to get from city A to city B but I want to go through National Park C along the way).

It's worth seeing what Google Maps can do today in the hands of someone who is used to the app and uses it aggressively. Apple still has a lot of features to add.

(And, for BOTH of them, it's still really early days. They both, for example, can't tell you where public toilets might be, or where one can mail letters. They both have lousy walking directions. They both have no mechanism for "suspending" a current search or route to open a second page to do something else. They both have lousy and limited abilities to share routes or anything else, let alone plan a joint route together over the internet. They both have no mechanism for anyone to provide a list of "attractions to see along I15 between Las Vegas and LA" sort of feature. etc etc.)
[doublepost=1469647295][/doublepost]Oh forgot to add that Google, right now, handles lack of coverage much better than Apple. They both suck when coverage is not available (they both seem to hold onto basic nav info even with no coverage, but god help you if you try to edit that route while there is no coverage), but at least Google has the ability for you to manually force the download of some material in an area where you think there will be limited coverage.

And of course Google has lane indicators (which of multiple highway lanes to move into for an upcoming turn).

Many of these things I've listed don't seem to matter when you are driving day to day along the same route, but they matter a LOT when you are driving in unfamiliar territory. Apple could solve some of them today, even without requiring huge data collection efforts. For example Apple could be a lot more aggressive in caching data and offering up (perhaps sub-optimal, and with no traffic info) routes even when there is no coverage. And hell, Apple could be using crowd-sourcing and/or telco's maps to WARN you about areas of upcoming no coverage (and preloading data just in case).

'2012 : Google Maps >> Apple Maps... Apple spent 4 years to improve Apple Maps...
'2016 : Google Maps >>>> Apple Maps...

Great buy, Apple.

Sigh... I was looking for directions to my doctor's office yesterday. Of course Apple Maps is useless in this regard.

Let's see, how about I search for "Dr X". Apple Maps directs me to some place out of state with "Dr" in the name.
I did the same with Google Maps. Google Maps finds my doctor's office! Wow, was that so difficult?

Again, Apple Maps is the stupid assistant that only understand literal strings. Context shmontext.

I find Apple Maps more attractive and easier to use than Google Maps, but GMaps has certain advantages that are undeniable, for example:
- search along the route (eg, for gas stations, food, or lodgings, while in nav mode, and ON the already programmed route)
- display of useful information for some searches (eg price at gas stations, price for lodgings). These may not be perfectly accurate, but they allow you to rapidly scan eg the expensive hotels from the cheaper ones
- pretty much everything related to search (including "unusual" searches like "where do locals eat")
- much more willingness to utilize crowd-sourcing for all sorts of purposes including things like allowing users to easily and rapidly rate establishments and determine favorites. Apple's obsession with privacy is (IMHO) preventing them from handling a number of use cases that they could, at worst, just allow people to opt into.

- Google has a mechanism (lousy and painful, but at least it is there) for establishing way points along the way (eg I want to get from city A to city B but I want to go through National Park C along the way).

It's worth seeing what Google Maps can do today in the hands of someone who is used to the app and uses it aggressively. Apple still has a lot of features to add.

(And, for BOTH of them, it's still really early days. They both, for example, can't tell you where public toilets might be, or where one can mail letters. They both have lousy walking directions. They both have no mechanism for "suspending" a current search or route to open a second page to do something else. They both have lousy and limited abilities to share routes or anything else, let alone plan a joint route together over the internet. They both have no mechanism for anyone to provide a list of "attractions to see along I15 between Las Vegas and LA" sort of feature. etc etc.)
[doublepost=1469647295][/doublepost]Oh forgot to add that Google, right now, handles lack of coverage much better than Apple. They both suck when coverage is not available (they both seem to hold onto basic nav info even with no coverage, but god help you if you try to edit that route while there is no coverage), but at least Google has the ability for you to manually force the download of some material in an area where you think there will be limited coverage.

And of course Google has lane indicators (which of multiple highway lanes to move into for an upcoming turn).

Many of these things I've listed don't seem to matter when you are driving day to day along the same route, but they matter a LOT when you are driving in unfamiliar territory. Apple could solve some of them today, even without requiring huge data collection efforts. For example Apple could be a lot more aggressive in caching data and offering up (perhaps sub-optimal, and with no traffic info) routes even when there is no coverage. And hell, Apple could be using crowd-sourcing and/or telco's maps to WARN you about areas of upcoming no coverage (and preloading data just in case).

That's a really good summary, thanks!

I agree with all those suggestions. Caching for offline is a huge feature.

One thing I would love for all driving navigation apps to add are landmark-based directions.

For example, "turn left in 2000 feet" is a pretty useless instruction. How is a normal person supposed to estimate 2000 feet while driving at 40mph? Or, "turn left on to main street, route 40a west, route 16 west." Thanks for letting me know this road has 3 names, now I have to look out for either a tiny street sign, or one of two state road signs.

Instead, they should leverage their POI and streetview database to say "turn left at the Dunkin' Donuts" or "turn left after the yellow barn." Between POIs and object recognition in photos, they should be able to put together these sorts of directions.