iOS 6: Setting Apple Maps expectations
Maps are core technology on a smartphone these days. We depend on our phones to make calls and otherwise keep us in contact, and we depend on them to tell us where we are and help us find where were are going. We depend on them. Messing with a successful mapping solution on mobile, in any way, is non-trivial. They're an incredibly important feature and one Google, Nokia, and TomTom have spent years building out. How will Apple match all that in iOS 6?
Until relatively recently there were two places to get maps, NavTeq, which is now owned by Nokia, and TeleAtlas, which is now owned by TomTom. If you wanted maps, you had to license the tiles from one of those two companies. OpenStreetMap is an attempt to crowd source an alternative, but it's not there yet, and arguably it will be better for casual rather than mission-critical use for a while to come.
Microsoft used Navteq. Apple used Google. Google originally licensed maps from TeleAtlas, but eventually replaced it with their own data. (This is broadly similar to both Apple and Google originally using Skyhook for Wi-Fi router location mapping, and both replacing Skyhook with their own location databases.)
Google didn't just re-map the world, however. They sent out trucks and photographers, and made Street View. They redrew bitmap tiles as vectors. They added social tracking in Latitude. And they gave away free turn-by-turn Navigation.
Apple reportedly wouldn't integrate Latitude into iOS Maps, and Google reportedly wouldn't give them Navigation. Street View came to iOS but the vector tiles didn't. Driving, walking, and public transit routes, and alternate routes, appeared. And Google collected and monetized the data that was returned from each and every query.
That's a problem for Apple. As much as Google was Apple's partner at the original iPhone launch, they are now Apple's biggest, most heated competitor.
That's also a problem. For Apple to reproduced all the work done by Google from Maps launch to today would be non-trivial. Even for a company with $100 billion in the bank, it would necessitate a herculean effort.
But Apple's been planning it for a while.
In July of 2009, Apple bought Placebase and integrated the founder into their Geo Team. As far as I can tell, Placebase didn't have their own maps, but instead focused on innovative ways to integrate a variety of public and private datasets, and layer them over the maps.
In July of 2010, Apple bought Poly9. It's not clear to me what Poly9's core business was, but they did surface a product called Poly9 Globe. It was a browser-based 3D geolocator -- essentially a Flash-based web app that looked like a spinning globe and could tell you where things were and exposed APIs to big corporate clients. That sounds like Google Earth style map data visualization technology, however. And since they licensed their maps from others, including Google, there still aren't any maps.
In August of 2011, Apple bought C3 Technologies. What C3 Technologies did, and now presumably does for Apple, is fairly clear. They make photo-realistic 3D map renderings. Think Google Earth, but with real little city models you can move through. Yet once again, this is visualization, and not core map data.
Putting it all together (or taking it all apart)
Placebase and Poly9 and C3 Technologies all add up to a killer way to render maps in 3D and layer interesting information over them.
But Apple still needs the maps.
While Apple turned to OpenStreetMaps for their recent iPhoto for iOS app, I'm not sure OSM could provide the consistent quality of maps Apple would need for a more critical service like iOS Maps. That leaves redrawing maps, the way Google did. Or licensing directly from Nokia or TomTom. Nokia seems unlikely, for the same competitive reasons as Google. That leaves TomTom.
Street View is also not easily duplicated. There haven't been widespread reports of Apple cars or jetpacks photographing alleyways and strip malls, the way there was when Google was in the middle of creating Street View. It's possible Apple hired or licensed out that work, but it's hard to imagine any large scale photo mapping service going unnoticed anymore.
Traffic data is another factor to consider. Apple says they collect traffic data but has never been clear if that's network traffic, actual roadway traffic, or both. In many ways, however, Apple has the ultimate crowd source at their disposal -- hundreds of millions of iOS users with GPS reporting their locations in cities around the world.
Public transport directions would have to be replicated or likewise licensed. And the list continues to grow.
More than features, reliability and accuracy will be far more important concerns at the outset. That's true both for users, who rely on it for mapping, and developers who rely on the APIs that call it to give users mapping in other apps.
The Google-fed Maps app is imperfect and hasn't seen any significant feature upgrades in years, but it's really good. There's a high bar for Apple to clear, and again, Maps are core technology now. Having bad maps is like making bad calls or dropping communications. Apple has to clear that bar, quickly and convincingly.
Apple did launch iCloud last year, so they're perfectly capable of deploying data intensive new services. But how many, and how fast?
Arguably iCloud didn't launch feature complete. iTunes in the Cloud and iTunes Match rolled out over time. Documents in the Cloud is still waiting on Mountain Lion before it'll work in Apple's own iWork for OS X. And new services like photo and video sharing, and new Reminders and Notes web apps are rumored to be coming just as iCloud hits its first birthday.
No company, not even Apple, can do everything. And certainly not all at once. Time and effort spent in one area can't also be spent in another. When Apple was rushing to get the original iPhone out, they pulled engineers from OX S and Leopard was delayed.
It doesn't seem likely Apple would pull engineers from Mountain Lion, iCloud, or Siri to catch up to years of Google Maps development.
iOS 6 Maps
What seems likely with iOS 6 Maps is that Apple will do what they've historically done -- relaunch with a subset of next-generation features that don't do everything the previous generation does, but do a few things in an entirely new and better way.
The original iPhone was like that. It didn't do everything the Palm Treo or BlackBerry did, but the capacitive multitouch interface was so good people bought into it anyway, even if they grumbled a bit while doing so. The new versions of iMovie and Final Cut Pro X have both been like that. Amazing, visionary new products missing key features of the older versions, made slowly better over time.
That strategy worked magnificently with the iPhone, passably with iMovie, and the jury is probably still out on Final Cut Pro X. The iPhone has such a great multitouch interface people were willing to wait for the missing features. iMovie and FCPX are niche products that, while frustrating, don't frustrate the mainstream. Maps will.
Given the limits of time and space, it seems the most likely scenario of Apple Maps is basic mapping functionality, amazing visualizations, and perhaps some cool additional data layers.
Some features could be U.S. only, or major markets only, at least at first. Certainly, some will have to make for visually exciting demos on the WWDC stage, and later in iPhone 5 commercials.
"Siri, give me turn-by-turn directions to 1 Infinite Loop", rendered like something straight out of Pixar, would certainly fit that bill.
And that's pretty much all I'm expecting from iOS 6 Maps. Not a feature-for-feature replacement of the current Google-fed Maps app with pure Apple tech and polish, but something with a lot of eye-candy, that over time adds back the most important features and introduces new ones. And eventually, maybe by iOS 7 or iOS 8, a damn good mapping solution.
Addenda: Google Maps redux
What will be interesting to see is if Google, free of the shackles of Apple's built-in Maps, submits their own Google Maps app proper to the App Store. Given the brouhaha over Google Voice, Apple would almost certainly have to approve it. (It might even be in their best interests to approve it, to take the pressure off Apple Maps in its early days.)
If that happens, iOS users would actually be better off than every before -- pure Google and pure Apple maps apps to choose from, or to alternate between. The best of both worlds (or both companies mapping the world).
- iOS 6: The multi-billion dollar balancing act
- iOS 6: Higher hanging fruit
- iOS 6: A fresh coat of paint
- iOS 6: Is it time for Apple to revamp the multitasking fast app switcher?
- The 16:9 iPhone
- The 4 inch iPhone
- How Apple could provide direct document access in iOS 6
- iOS 6 and the opposite of widgets
- Is it time for Apple to revamp the Home screen?
- The challenge of bringing Siri to the iPad
- iOS 6 and privacy: How Apple should draw inspiration from Android for better app
Some of the above spun off from a chat with @markgurman of *9to5Mac, so credit where it's due -- though he may or may not agree with the rest of it*
Have something to say about this story? Share your comments below! Need help with something else? Submit your question!