# Apple Launches the MapKit for Automotive SDK, First With Ford > Source: > Published: 2026-07-24 08:14:44+00:00 Apple and Ford today announced that Apple Maps will be integrated directly into Ford’s upcoming Universal Electric Vehicle (UEV) Platform through Apple’s new MapKit for Automotive SDK. Coming to Ford’s UEV Platform in 2027, this integration will deliver a beautiful and easy-to-use navigation experience powered by Apple Maps directly to the vehicle’s displays. Road-level Maps information will also enable Ford’s Latitude AI team to build a seamless hands-free driving experience. Leveraging Apple’s new MapKit for Automotive SDK, Ford’s Universal Electric Vehicle Platform will offer drivers turn-by-turn directions using natural language, real-time traffic and incident information, intuitive search featuring detailed place cards, and routing options to help users easily find the best route to their destination. Additionally, Ford UEV drivers will benefit from an intelligent EV routing functionality, including battery preconditioning. Ford will also use road-level information from Apple Maps as part of the development of its next-generation BlueCruise hands-free highway driving capability to deliver a more seamless on-ramp-to-off-ramp experience. Apple services have historically been sold as complements to Apple hardware: Apple Maps, [for a decade](https://eshumarneedi.com/2024/07/27/apple-maps-launches.html), had been limited to Apple devices, replacing Google Maps. That is no longer the case; Apple TV is a canonical example of Apple’s interest in broadening the Apple services market. Similarly, this new MapKit SDK — short for software development kit — is an intentional expansion of Apple’s services market following the abject failure of [CarPlay Ultra](https://www.apple.com/newsroom/2025/05/carplay-ultra-the-next-generation-of-carplay-begins-rolling-out-today/), a version of CarPlay meant to consume the entire car software experience. Even CarPlay’s most fervent supporters, like BMW and Ford, haven’t adopted CarPlay Ultra because it exerts too much control over a driver’s experience. The CarPlay Ultra gambit was clearly an effort to make *something* out of the Apple Car project, also a failure. Ultimately, I think the CarPlay Ultra fiasco is indicative of the two opposing yet symbiotic forces within Apple: the product people and the services people. The product people want Apple to own as much of the “stack” as possible: the hardware, the software that hardware runs, and the services that software sells. They wanted to build a car, make software for it, and sell services through that software: that was Project Titan, the car project, in a nutshell. That is fundamentally the same strategy that governs the Apple Watch, MacBook Neo, even the iPhone. The services people, like those in charge of Apple TV and its content acquisitions like Formula 1 and Major League Soccer, don’t believe in that because they’d rather make money through advertisements and subscriptions. They paid hundreds of [millions of dollars](https://www.reuters.com/lifestyle/sports/major-league-soccer-apple-tv-agree-10-year-partnership-2022-06-14/) in upfront costs for MLS and F1 to sell more subscriptions, even to people who have never owned an Apple device. The services people won here, largely because the product-driven CarPlay Ultra / Project Titan strategy — to own as much of the software experience as possible — failed. No car manufacturer was interested in that. Perhaps consumers would’ve been, since CarPlay by itself is overwhelmingly popular by [Apple’s numbers](https://www.youtube.com/live/q5D55G7Ejs8?t=2290), but it didn’t matter anyway because the difference in experience for iPhone users and non-iPhone users was too stark. (Not to mention, it was too much work for very little tangible benefit on the manufacturers’ end.) So now, Apple Maps — just like [Apple Music](https://rivian.com/newsroom/article/apple-music-and-rivian-introduce-immersive-spatial-audio-with-dolby-atmos-experience-to-rivian-drivers) in Tesla, General Motors, and Rivian vehicles — is a *service* built to make money independently. It doesn’t matter whether someone owns an iPhone or not, because they’ll still be forced to use Apple Maps in their Ford vehicle. And most importantly, they’ll be forced to look at Apple’s advertisements [coming to Apple Maps soon](https://ads.apple.com/maps). The ads part is a tragedy because it signals a definite end to Apple’s product-driven mindset. Before Apple started putting ads in Apple services, they were also Apple *products* — you *buy* a subscription to Apple Music. Now, Apple services are partially ad-driven enterprises, where your use of the service itself draws revenue. In creating the MapKit for Automotive SDK, Apple doesn’t care about people spending money at the Apple Store or on in-app purchases. Apple isn’t delivering a product to consumers as much as it’s guaranteeing engagement to ad buyers. The consumers are not the primary consumers; corporations who pay Apple are. This is against the very philosophy Apple in many ways [was founded upon](https://daringfireball.net/2026/07/ads_on_apple_news_suck): making high-quality *products* for consumers willing to pay premium prices. Modern Apple would probably object to the characterization that ads in Apple services cheapen the experience, but it’s true: ads in Apple Maps do not make for a premium experience. The new Apple doesn’t seem to care about that. It’s uninterested in delivering a premium experience, and it’s uninterested in asking for your money to deliver that experience. Ergo, the MapKit for Automotive SDK.