It's defensive, (and it was built at a time when money was free).
The iPhone launched with Google Maps. Then Google decided to push feature updates skewed towards android phones, leaving iPhone users behind. Apple saw that a vendor could screw their users over (and potentially cause defectors), and decided to invest to ensure they don't have a dependancy.
The best part is that they can now offer it to App Store developers as a free iOS SDK (and paid API on web). Meanwhile the same developers would have to pay an exorbitant cost to use Google Maps. It's part of the moat that makes iOS the more profitable platform to develop for. You can also see this playbook with the release of free Weather APIs.
Yea Apple/Google maps has to be expensive to build and maintain, but at least for apple, they were able to buy their way to bootstrapping the map. What's impressed me is all the fly-over and custom 3D modeling they've done. It does really feel like they just wanted to make a good map at some point, even beyond what people needed or expected. That said, mapping products probably has good caching and fault tolerance you can design in to reduce cost - maps don't go out of sync that fast (for caching) and you'd never know if their "suggested routes" data was out of date occasionally, because you can never drive both routes at once.
At the time, Google Maps on iOS was written by Apple, not Google, and Google was holding back API access for Street View until Apple sent back more location/tracking/demographic data on users that Google wanted.
Rather than sell out their users, Apple dropped Google Maps as the backend and launched their own maps, and then let Google write their own Maps app where they could do anything they wanted.
> The best part is that they can now offer it to App Store developers as a free SDK. Meanwhile the same developers would have to pay an exorbitant cost to use Google Maps.
Apple Mapkit is free up to 25K api call a day, after that you have to contact Apple for more (and pay I guess?).
The iPhone launched with Google Maps. Then Google decided to push feature updates skewed towards android phones, leaving iPhone users behind. Apple saw that a vendor could screw their users over (and potentially cause defectors), and decided to invest to ensure they don't have a dependancy.
The best part is that they can now offer it to App Store developers as a free iOS SDK (and paid API on web). Meanwhile the same developers would have to pay an exorbitant cost to use Google Maps. It's part of the moat that makes iOS the more profitable platform to develop for. You can also see this playbook with the release of free Weather APIs.
Yea Apple/Google maps has to be expensive to build and maintain, but at least for apple, they were able to buy their way to bootstrapping the map. What's impressed me is all the fly-over and custom 3D modeling they've done. It does really feel like they just wanted to make a good map at some point, even beyond what people needed or expected. That said, mapping products probably has good caching and fault tolerance you can design in to reduce cost - maps don't go out of sync that fast (for caching) and you'd never know if their "suggested routes" data was out of date occasionally, because you can never drive both routes at once.