Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Prediction: This thread gets incredibly out of hand, with people imagining that this new Maps app will do all sorts of impossibly amazing things, and then when it comes out they all say how much Apple sucks because they didn't include whatever stupid, obscure feature they imagined!
 
This story has nothing to do with what you mention. Apple can already build what you mention using Google's map data.

This is simply about replacing the provider of maps and the locations databases behind it. This has nothing to do with Maps.app, which is a barely functionning mess of basic functionality on iOS compared to what the competition has to offer.

The efforts Apple is putting towards this back-end infrastructure would be best spent on making the front-end application better. If only Apple didn't operate in a "small business" mode where they have small teams that do many different projects depending on priorities rather than more teams working on more stuff at the same time.

There is greater cohesiveness in small organizations. By having so few employees, Apple is able to maintain the "start-up" culture. Contrast this with Microsoft which employs almost twice as many people as Apple, and Microsoft doesn't have a retail division like Apple (I'm betting the bulk of Apple's employees are Retail). There have been reports that Microsoft suffers from political infighting which have played a role in delaying Microsoft's entry to new markets.



It's also not a very good comparison in the fact that Safari wasn't built from the ground-up by Apple. They basically took years of work done by the KDE Community, forked it, promised to give it back (according to the terms of the GPL), went underground, showed back up a few months later with an uintegratable mess, basically screwing the original developers out of the improvements they made.

Go back to your first paragraph. The Maps.app is a NATIVE maps application, which admittedly doesn't offer the same functionality that competitors' native maps applications do offer (e.g. Android). But there are plenty of apps that can fill the gap. With Safari, you're saying that Apple screwed the original developers over. If Apple implemented features like turn-by-turn in the Maps.app, that would supplant developers who have those kinds of apps in the App Store and put them out of business.
 
If I'd been betrayed as badly as Apple was by Google, I'd screw them as deeply as I could.
 
There is greater cohesiveness in small organizations. By having so few employees, Apple is able to maintain the "start-up" culture.

The problem is that they often release half-baked stuff only to never update it again, or before a long time has elapsed. They start strong, only to then let the competition catch up, pass them and they seem to concentrate ressources again only when they are then playing catch up themselves.

This often leads to situations like the current one with the Maps application on iOS.

Go back to your first paragraph. The Maps.app is a NATIVE maps application, which admittedly doesn't offer the same functionality that competitors' native maps applications do offer (e.g. Android). But there are plenty of apps that can fill the gap. With Safari, you're saying that Apple screwed the original developers over. If Apple implemented features like turn-by-turn in the Maps.app, that would supplant developers who have those kinds of apps in the App Store and put them out of business.

Completely different situations that have nothing to do with each other. Apple did not compete on features against KDE, they used KDE's hard work and created more work for them in the process, both profiting and leaving the work on integrating back their "contributions" to the community. It created a lot of ill will and disappointment after they had made promises of working closely with the KDE developers.

This has nothing to do with 3rd party vendors trying to add functionality to the device that should simply be there in the first place. A lot of App Store fluff is like that, stuff that Apple should've implemented themselves long ago. You do realise Apple gets a lot of their "new features" ideas for iOS straight from App Store submissions right ?
 
I wouldn't say so.
My father has an iPhone 4 but recently bought himself the latest Tom Tom. £150 for a device that he'll be taking all over Europe, whereas if he was to do this with his iPhone the data cost would be massive. Beyond the initial cost there's nothing else to fork out for. And it also has free over-the-air traffic updates too and can be updated through customers making new points of reference, etc.

For most people the iPhone GPS is enough, but it's not the best at all.

i got the tomtom app (all western europe) £40 and i can listen to music at the same time as it all charges and is a great solution. data charges? what data charges? its all on the device!

between that and the fact that more and more cars have satnav built in i guarantee the stand alone will become a very niche product.

specialist hikers ones will survive but not much else
 
Waze is awesome. It is an Israeli-based company. Virtually any smartphone user in Israel uses it, on iPhone, Android, Nokia and Windows Mobile. The traffic data and accuracy is unbelievable. Sometimes it takes me through weird routes just to bypass traffic jams. You also have ways to report accidents, speed cameras, traffic police etc.

Here's a link to a typical daily use in Waze, every car you see is actually a person using the software while he drives, shown up on my iPhone screen in real-time.

http://news.cnet.com/i/bto/20090521/waze-Israel_screen_shot_610x328.jpg

Oh, and did I mention that it is completely free?
 
Not even a bit...
If I am 5 days in the mountains... I need to change some batteries... I cant do that on the iPhone. And I am not going to take 5 3th party batteries with me. I need the space for food and drinks and maybe even a bit of soap.

These things are fun ... but when you use GPS like we do.. its a no-go.

So there will still be 50 - 100 of them sold per year.
 
When the only function I need is driving directions and all it has is a line drawn I need to constantly stare at while driving, yes it is a barely functioning mess. It's barely providing the function I need out of it. That makes a whole lot of mess of my driving experience.

So the application isn't a mess, it provides a lot of mess of your driving experience. Two different things.

And the application isn't barely functioning. It's providing barely the function you need, since for example I don't need that function and for me the app functions as great as any other maps app. So it's about the features of the app being insufficient for your needs. Not that the app is not working well.
 
Here is the funny part in all of this.

Google could have OWNED the mobile market.

Originally Google didn't compete with Apple in the mobile market so there was an incentive for Apple to use Google services on the iPhone.

Now that Google is in direct competition with Apple, Apple has an incentive to keep Google services off the iPhone.

Same goes with Nokia and RIM.

None of these companies has an interest in search (user data/advertising) and would have been happy to help Google dominate the market.

Yet Google felt the need to come out with Android to get a market it already owned. Now that Google is competing with these other companies, they have an incentive to invest in technology instead of leveraging Googles technology.

In a round about way, its all pretty pointless.
 
Wirelessly posted (Mozilla/5.0 (Linux; U; Android 2.3.4; en-gb; Google Nexus S Build/MIUI) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

The end of the standalone GPS unit is nigh.

To be honestly I do not see it. The map finding of lets say my Atrix with its navigation is still not as good as my older dedicated Garmine Navi from 2007 (even with outdated maps)

I have used google map to help find the address then I would enter it into my Garmin and use that for finding the route.

Google Maps is fantastic. The app itself on iToys could be improved, but why go to the effort of making a whole new map format and collect data when Google has it all already?!

I would not think they are removing Google as their source of map data but more doing away with good for the mapping algorithums and route finding.
The current reason Maps sucks on iOS is Apple failure to updated. It lags way behind everything else.
 
Also...

.. i think a lot of the fun things you get with the iphone, eg: google maps with XYZ function only works in the US, with (if we're lucky) slow roll outs to the rest of the world. Then on top of that you have the issue with data services like maps being very slow if your provider has a less then reliable network!

My point being, I personnely wouldn't be using this as a "should i buy or not" reason. If it does work in my given country, then its a brilliant extra!
 
Last edited:
Hmmm maybe there is a new Map app on the iPhone 5 (4gs or what ever they call it) and Googles agreement is for iPhone 4.... Which I assume will be the discounted phone when 5 comes out....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.