The encyclopedia · Product & Design · Product decision · 2012
Apple shipped Maps so broken that Tim Cook apologized and told users to try Google's
In 2012 Apple replaced Google Maps with its own, half-finished Maps. Wrong directions and missing cities forced a rare public apology from Tim Cook.
Apple · Google · 2012-09-19
What happened
When Apple released iOS 6 in September 2012, it did something it had never done before: it removed Google Maps, which had been the default maps app on the iPhone since 2007, and replaced it with its own Apple Maps. The split had been building for years, as Google and Apple grew apart and Google kept the best navigation features for Android. Apple wanted to control its own maps. The problem was that its maps were nowhere near ready.
At launch, Apple Maps was riddled with errors: wrong and even dangerous turn-by-turn directions, missing or misplaced cities and landmarks, sparse public-transit data, and satellite imagery that looked smeared. Users were routed to the wrong hospitals, sent down dead ends, and told to drive across bodies of water. Because Apple had made its own Maps the default and pushed Google's to the web, hundreds of millions of iPhone users were suddenly stuck with the inferior product.
The backlash was swift and global. In a rare move for Apple, CEO Tim Cook published an open letter of apology, saying the company had 'fallen short,' and — in a line that stunned the industry — recommended that frustrated users try competitors' mapping services, including Google's, while Apple fixed its own. The senior executive who had overseen iOS software, Scott Forstall, left the company in the reshuffling that followed. Google Maps returned to the App Store that December and shot to the top of the charts.
Why it happened
- Apple shipped its own Maps as a forced replacement for a mature, depended-on product before it was anywhere near feature- or quality-complete.
- Strategic motives (reducing dependence on Google, controlling the stack) outran the product's actual readiness.
- Making Apple Maps the default and demoting Google Maps to the web removed the safety net for hundreds of millions of users at once.
- Map data quality — the hard, unglamorous part — had not been validated at real-world scale before launch.
The lesson
Replacing a product your users depend on is a high-stakes swap, not a feature launch. Ship the new one only when it's at least as good as what it replaces — or keep the old one available meanwhile.
Aftermath
Apple spent years steadily rebuilding Apple Maps, eventually overhauling its underlying data and winning back many users; the app is now generally well regarded. But the 2012 launch remains the canonical example of a platform owner shipping an inferior first-party replacement for a beloved third-party product, and of the reputational cost of doing it before it's ready. Cook's apology — and his suggestion that Apple customers use a rival's app — is still cited as a masterclass in how to handle a public product failure with honesty.
Sources
spotted an error? The club wants to know.
Comments · 0
Sign in to join the comments.