Eddy Cue and Apple Maps team members describe how they are rebuilding the product from the ground up to eventually own the entire map stack, like Google does
The company is rolling out more detailed maps built from its own data for the first time — I'm not sure if you're aware, but the launch of Apple Maps went poorly.
Context & Ripple Effects
The arc here runs from disaster to vertical integration. After the 2012 Maps debacle forced Apple into public beta testing for iOS releases, Eddy Cue has repeatedly framed Maps as a never-ending rebuild rather than a finished product, telling Fast Company why Apple keeps iterating on it instead of declaring victory.
What changes now is the data source: per the related coverage, Apple is rolling out maps built from its own survey data for the first time, starting with a San Francisco Bay Area release that analysts found had better road data than Google's but weaker location data — evidence both of the strategy's promise and how far behind the first rebuilt regions still are.
First-order effects
- Apple begins replacing licensed third-party map data with its own collection region by region, making its data suppliers' largest mobile customer a shrinking one and putting map quality directly under Apple's control for the first time since launch.
- Users in early rollout regions like the Bay Area get noticeably different maps — better roads, worse points-of-interest — so the rebuild lands as uneven quality across geographies rather than a single upgrade.
Second-order effects
- Google's map stack becomes the explicit benchmark Cue names publicly, raising the bar for every subsequent Apple Maps release — including the iOS 13 update positioned as the service's biggest yet — and forcing comparisons on Google's home turf of data completeness.
- Map data vendors face a structural erosion: each region Apple self-surveys is revenue permanently removed from licensing, pushing those suppliers toward other customers or consolidation.
Third-order effects
- Owning the entire map stack turns Maps from an app into proprietary infrastructure — the same data-rights logic seen in Cue's earlier framing of Maps as perpetual work — positioning Apple to build services (navigation, AR, eventually autonomy-adjacent features) on data no competitor can license away.
- If the pattern holds, consumer mapping splits into two fully vertically integrated stacks — Apple's and Google's — with everyone else renting, a consolidation driven by the fact that ground-truth data collection is too expensive to outsource at the top tier.
The trend: Platform companies are pulling their most strategic data layers in-house, converting licensed inputs into owned infrastructure they can differentiate on and deny to rivals.