Apple Maps: Ship Before It's Ready?

It's mid-2012. You are Scott Forstall, Apple's powerful SVP of iOS Software. For years, Google Maps has been the default, pre-installed mapping application on the iPhone, functioning as a massive driver of consumer value.

However, tensions with Google (who is dominating the broader smartphone market with Android) are at an all-time high. Google is weaponizing their maps data by withholding turn-by-turn navigation from the iOS version of Google Maps to keep it an Android exclusive. Steve Jobs had vowed to go to "thermonuclear war" against Android, and this is the front line.

In response, Apple has decided to build its own mapping service from scratch, combining data from TomTom, OpenStreetMap, and several acquired startups.

iOS 6 is weeks away from launch. Apple Maps looks beautiful with its vector-based graphics and new 3D Flyover feature. But internal testing shows major issues: mislabeled cities, distorted satellite imagery (bridges looking like melted Dali paintings), and dangerous routing errors that lead drivers into lakes.

This is a Tier 1 League Match. The decisions are binary and the consequences are terminal for your career.

The principle: Never ship a core, trust-based utility before it matches the incumbent's quality, even if the incumbent is your rival. Strategic independence is useless if it costs you user trust.