3 ms·
The article does not really provide much new information. That mapping is hard is known. That there are companies who have much experience in this area and that
by lispm 14y ago
The article does not really provide much new information. That mapping is hard is known. That there are companies who have much experience in this area and that Apple will have to compete with them is known - from Google, over Garmin to Nokia.
It's just that it is hard and that it will take Apple a lot of time and investment to bring the mapping functionality to a better level. I'm pretty sure Apple knows that.
It's just the first iteration. Apple works that way. Bring a product or service in a first iteration and then improve from there. This is how the iPod evolved, for example. Aperture, another example.
The current maps application in iOS already has a feedback interface. This helps to improve the data.
But there are a few things which need more consideration:
* the 3d view looks ugly when looked at close to the objects. The 3d reconstruction algorithm which creates a 3d view from images is problematic.
* the angle of the data from Tomtom is for car users. Other users have less benefit: there is a lack of detail and the usage perspective renders the map in a certain way. For example here in Europe there are a lot of local public transit users. They have a hard time identifying useful informations on the current maps.
* combination with all kinds of POIs. You need to get that data and have it constantly updated. Where is a shop, when is it open, where is a museum, where are interesting views, where is a difficult road condition, ...
Probably the mapping domain is the toughest Apple has touched in years. You need a really good idea how to deal with the challenges. Personally, I think it is worth it, but it will be a lot of work (and not of machines, but also of humans) and very expensive for Apple. I'd wish they would use more of Openstreetmap and that there would be a benefit for the Openstreetmap community.
- blrgeek 14y agoThe article actually breaks down the exact lacunae in Apple's approach - it's certainly has more map domain specific insight than all the other articles on iOS6 Maps put together. And it has recommendations which are very specific and not hand-wavy. From the article 1. Completeness – Features are absent and some features that are included seem to have erroneous attributes and relationships. 2. Logical Consistency - Expecting the data across different sources to be completely consistent ie 'An example of this could be having a store’s name, street number and street name correct, but mapping it in the wrong place' 3. Positional Accuracy – is considered the closeness of a coordinate value to values accepted as being true 4. Temporal Accuracy – particularly in respect to temporal validity – are the features that they map still in existence today? 5. Thematic Accuracy – particularly in respect to non-quantitative attribute correctness and classification correctness.
- cookiecaper 14y ago>It's just the first iteration. Apple works that way. Sure, all software works this way. We all know the "release early, release often" mantra. The difference is that Apple replaced functionality that many users depended upon with something completely inadequate. It'd be like Sun or IBM going in and replacing all the super specialized custom microprocessors in your server farm with experimental souped-up 386es. Sure, they're the same type of thing, and hypothetically they should serve the same function, but you don't just go out and replace completely functional stuff without at least the basics firmly in place. It is clear that Apple released iOS Maps very prematurely, mid-development. This was stupid, and there's really no use splitting hairs about it. Some bugs or problems are to be expected, but a critical function that most of your users depend upon, that has real, serious consequences if failure occurs (lost in a dark alley, etc. etc.) ought to be better than what Apple has put out. Add to this Apple's draconian policies that forbid Google from offering "Google Maps" as a third-party app on the App Store (though I guess today it looks like they may be waffling a bit on this), and you have a very serious problem. I guess we can say that it may be good for Android adoption. :)
- fpgeek 14y ago> This is how the iPod evolved, for example. The first iPod didn't do a lot, but what it did, it did correctly. If the first iPod had had the scale of quality issues we're seeing out of Apple Maps, there wouldn't have been a second.
- InclinedPlane 14y agoYou can get away with releasing a flawed first gen product as long as you are forging into a new field. Both the iPod and the iPhone had plenty of competitors, but they were also so massively differentiated from the rest of the market that they effectively created new product categories (especially the iPhone). When you try to compete with an entrenched product that is feature rich and highly polished (such as google maps) you either need to differentiate your product or come to the table with an equal level of polish. Apple has failed to do this. They have made a classic "strategy tax" blunder. This move is straight out of the playbook of the old, bad Microsoft and the old, bad IBM. It's the sort of fundamentally bad idea that a big, dumb, lumbering company makes. If there's anyone in the world that is happy about this it has to be the people on the surface team at Microsoft. Because it shows how massively vulnerable Apple is to competition now. Whatever magic Apple used to have, it seems to be gone.
- corporalagumbo 14y agoIf you can call selling millions of iPhones in the blink of an eye magic, then I'd say Apple still has plenty, no?