Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't get why Earth and Maps were ever different products. OK, so Apple might have objected on iOS, but what about the other platforms? And they probably wouldn't have - there are other mapping products in the app store aren't there?
 
The fundamental problem is DATA, time for apple to drop some $$ and buy a proper dataset. Its not for the followers to devote their time, its for apple to buy a proper dataset.

I don't think Apple can even buy their way out of this one.

I haven't seen this posted yet (there are thousands of posts on the maps debacle), but here is an insight into how Google builds its maps

http://www.theatlantic.com/technolo...it-means-for-the-future-of-everything/261913/

TLDR: Google tweak every map by hand, they correlate with GPS and image data from their cars. The effort and attention to detail is astounding. Google's greatest competency is managing and indexing data.

The idea that Apple can roll out a few updates with some crowdsourcing is simply risible.
 
Last edited:
Aren't there existing apps for public transit info? (I don't live in an area that has a public transit system, so I have no idea what is available for people who do use pt).

Yes, but when it's not integrated into the default map, it's a lot of extra steps and greatly reduced functionality.

Let's say you're on a restaurant's web page in Safari. With Google Maps you would:

  1. Click the address
  2. Tap the pin
  3. Directions to here (from current location is already filled in)
  4. Tap the bus or walk icon (usually skip this step because bus is already clicked)
  5. Route

With this setup you can easily compare travel time between driving and transit, or get multiple transit routes.

When I was on vacation in Montreal, the Google Maps literally transformed the experience. Just type in "Mariott" and two taps later you've got your bus and subway route planned out and you've got a compass pointing you right the to bus stop.

With Apple Maps this list gets longer and involves multiple apps and a non-unified experience.
 
Looks like the doubling down on secrecy thing wasn't referring to what the iPhone 5 was going to look like. I wonder what else is in store?
 
looks like Apple may have played this one perfectly. Catch Google off guard, fix the problems as fast as you can, then by the time google does come out with something people will be used to Apple's map.

Yeah, that will happen - Apple Maps is almost beyond fixable.
 
"As with Google Maps, users can report problems to Apple to help improve the product."

Why do blogs keep saying this? It hardly matters to me that Apple Maps could be better in a couple of patient years when it's being a pain in the ass here and now. I went for an iPhone because it *wasn't* a fixer-upper OS.
 
100% agree... even I knew it was coming, Google will lose in the mid-to-long term because of this, and Apple will take a slight bashing in the short term. Give Apple's Map App about 2 years, and it will be the gold standard for mapping, maybe even one whole year.

I just wonder if Apple will allow it through a web-based interface ever, probably not...


it will be difficult for them to be the gold standard without a web site interface

also there are 3 counties (Tarrant, Denton and Dallas) in my vicinity, each one of their public transportation systems use Google for their trip planners (well one has their own also but it is dreadful)
 
Design? You are aware that Google has been doing map apps for a decade or something. They won't even have map testing to do, that goes on every day right now via Android apps and web access. Anything to tell someone here they are wrong, though. :rolleyes:

They have the data but the App would not of been design. Testing you need to make sure the data is coming in right, and working with everything.

iOS and Android are different beast to code for and have different design standards.

So again go learn how development really works. Any one who has an understanding of how large projects work for development understands that 3-6 months is very little time.
 
I hope Google *DOESN'T* hurry up!
As much as I prefer Google Maps over Apple's at the moment,
the more people use Apple Maps the sooner it will get better, and we'll all be better off for it!
 
I don't think Apple can even buy their way out of this one.

I haven't seen this posted yet (there are thousands of posts on the maps debacle), but here is an insight into how Google builds its maps

http://www.theatlantic.com/technolo...it-means-for-the-future-of-everything/261913/

TLDR: Google tweak every map by hand, they correlate with GPS and image data from their cars. The effort and attention to detail is astounding. Google's greatest competency is managing and indexing data.

The idea that Apple can roll out a few updates with some crowdsourcing is simply risible.

This. Apple's maps are all computer generated and that results with monstrosities like this one; Helsinki train station, the busiest spot in Finland's capital.

DKWpd.jpg
 
There is another part of this story that does not get mentioned... Did Apple think the gMaps App was good enough???

Even though Apple's map app is shotty now, the gMaps App did not have turn-by-turn for iOS, and was limited to Android use only. Apple saw them as being unfair, so they did what they did.

I still truly think Apple sticks to values/principals that other tech companies will never applaud or even empathize nonetheless.

Google should have made better updates for iOS... and Apple knew it for a long time.
 
Anyone else think Google is in no rush to help out a competitor platform? I don't see how it could take several months to make a maps app. Use the Android one as a basis. Or use the old iOS one as a basis. I mean, there were working navigation apps within a month of the App Store's launch...

iOS is a big money maker for Google, so what your suggesting makes little business sense.

The more entrenched Apple maps gets the less likely people are to use Google maps, in the same way Google Chrome will always be a mariginal player on iOS compared to Safari.
 
They have the data but the App would not of been design. Testing you need to make sure the data is coming in right, and working with everything.

iOS and Android are different beast to code for and have different design standards.

So again go learn how development really works. Any one who has an understanding of how large projects work for development understands that 3-6 months is very little time.

That is the word where I disagree. And half that time you claim they need is stupid meetings.
 
In Denver, Apple's Maps app works pretty well. The UI is very nice. But the lack of mass transit data is a really big disappointment for me.
Hopefull they can tap into that data feed sooner than later.
I've used iOS6 and the old maps three times to compare. In one case, iOS6 placed the address in the wrong location (Google's database has the same wrong address, but its maps somehow put the pin at the correct location.) They both found another restaurant equally correctly, but in one driving directions scenario Google offered a long windy mountain road rather than taking an exit further down the freeway as iOS6 and humans suggest. In this area (and with just three tests), it is a tie.

Unfortunately, interface for the transit directions of the old Maps app is still the best, even though HopStop is not that bad.
 
There is another part of this story that does not get mentioned... Did Apple think the gMaps App was good enough???

Even though Apple's map app is shotty now, the gMaps App did not have turn-by-turn for iOS, and was limited to Android use only. Apple saw them as being unfair, so they did what they did.

I still truly think Apple sticks to values/principals that other tech companies will never applaud or even empathize nonetheless.

Google should have made better updates for iOS... and Apple knew it for a long time.

Google didn't write the original maps app for the iPhone. Apple did.
 
This competition is good for us!!
Is that what you call Apple shutting Google out of the game? So we get to suck on a half-baked version for who knows how many months until Google's version is ready. And then good luck getting it approved by Apple quickly.

Yep, competition is good!
 
looks like Apple may have played this one perfectly. Catch Google off guard, fix the problems as fast as you can, then by the time google does come out with something people will be used to Apple's map. BOOM. As long as Apple gets the map together, I don't think anyone will care about google maps. Apple actually gave me a much better route to take yesterday than what google suggested.

"Played one perfectly"? More like botched it. I dunno about everyone else but I certainly didn't sign up for beta-testing. What pisses me off is Apple issued non-apology and no immediate resolution. If I enjoyed beta-testing products I would be using Android now. Hell, at that rate may be I will.
 
it will be difficult for them to be the gold standard without a web site interface

also there are 3 counties (Tarrant, Denton and Dallas) in my vicinity, each one of their public transportation systems use Google for their trip planners (well one has their own also but it is dreadful)

I do think a web-based map for Apple is truly needed, but the delivery will be different somehow, or maybe we'll just find it on the Mac App store sooner than later.

I think apple is planning to do a lot more convenience features in regards to planning/traveling than anyone of us on here have even dreamed of.

They are getting into mapping for a reason... and assuredly, hoping we'll see better customization to itineraries with passbook integrated now.

Apple will innovate with this... just wait. Another Apple ecosystem is coming...
 
and some one shows how little they understand about development and time it takes. If the thing was till on the drawing board and not in the design phase at all you then have a few months in design before you can really get cracking on the code part. Design needs to get a little lead on the development part.

It is not something can be slapped together in a few weeks or months. Something like this a fast time frame would be 6 months. That does not account for testing which they will do by far a better job than Apple did with its maps.
Sure, but it is Google's management fault for not having a basic app in development while many in the valley knew Apple was buying mapping start-ups and that was more than two years ago.
 
That is the word where I disagree. And half that time you claim they need is stupid meetings.

then you have other problems.
I work on a very large project. In terms of meetings I say I spend 15 mins every morning at one quick one that is there to get a status of everyone else on the team and what the status we are at. Good way to get a heads up on dependecy that might be an issue,

And then say I have another 3 hours every 2 weeks tied up in meetings. One is a team planning meeting to lay out what we are working on as a group, what we thing a as a group workload will be for certain parts and then end of an iteration meeting that really is good because we figure out what went good and not so good.

Other stuff it is broken down based on does it effect me or do I need to be involved.

On large project such as this you have smaller teams in side the teams. Say a design team. They handle design work so the developers are not wasting their time on it. They can stick to developing.

The Google map app is going to be a large project and have a lot of dependence on it.

----------

Sure, but it is Google's management fault for not having a basic app in development while many in the valley knew Apple was buying mapping start-ups and that was more than two years ago.

even if it was on the drawing boards and in plans Apple changed rushed them. They could of easily been planning on having another year as that is when the contract was up. Apple dropped it a year earlier than and took them by surprised.

It would of been stupid to assume it was going to happen a year earlier than the contract.
 
The more entrenched Apple maps gets the less likely people are to use Google maps, in the same way Google Chrome will always be a mariginal player on iOS compared to Safari.

Considering how Chrome just came out for iOS not even a couple of months ago, and is really nothing more than a skin for Safari you can't even set as default without jailbreaking...
 
I've used iOS6 and the old maps three times to compare. In one case, iOS6 placed the address in the wrong location (Google's database has the same wrong address, but its maps somehow put the pin at the correct location.) They both found another restaurant equally correctly, but in one driving directions scenario Google offered a long windy mountain road rather than taking an exit further down the freeway as iOS6 and humans suggest. In this area (and with just three tests), it is a tie.

Unfortunately, interface for the transit directions of the old Maps app is still the best, even though HopStop is not that bad.

are you kidding? transit is better on the new app

you pick transit for routing and your app. for NYC some apps will tell you when the next train is supposed to arrive at your station so you don't waste time waiting. as well as an service alerts. google never did that
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.