The WWDC hoopla around this tells me that Apple thinks of Apple Maps as an application, whereas in reality, maps are all about data—something Google understands better than anyone. Google maps are getting richer with data by the day. The more people use those maps to find locations, the deeper their data set gets. In my last visit to Old Delhi, I was able to find antique stores in back alleys with no difficulty at all. Apple Maps was nowhere close.
Malik suggests that Apple’s concern with their customers’ privacy may be holding back the quality of its maps relative to Google.
Google has faint regard for customer privacy, so they don’t hesitate to suck up all our data in order to build an amazing experience—so much so that many of us are willing to pay the price with regard to our personal information. Apple has a stance on privacy, which is why I am their customer, but at the end of the day, it’s an irrefutable fact that the Internet is a connected experience—and maps are part of that Internet.
Meanwhile, Reüel van der Steege has a side-by-side comparison of Apple’s upcoming Look Around feature with Google Street View.
Properly new in iOS 13 is Look Around, a feature similar to Street View in that it presents a three-dimensional street-level imagery, but with what appears to be a slightly different user interface (9to5Mac).
Other features announced include favourites, sharing and other items you’d expect from an online map service: Apple is essentially doing its best to catch up and be as feature-complete as the competition. That includes upgrades to MapKit, their developer toolkit (previously).
Apple now has a fleet of cars collecting data for Apple Maps. Since they’ve been making a point about consumer privacy lately, this page lists where their cars are going to be in the coming weeks. (AppleInsider notes that some of that data collection is pedestrian-based.) It turns out Google has a page for Street View data collection that includes similar information, though it’s far less granular: windows of several months, whereas Apple tells you where it’ll be within a two-week timeframe.
TechCrunch’s Matthew Panzarino reported last week on major changes coming to Apple Maps in iOS 12. The underlying data, which has come in for criticism since the service launched, is being redone. Rather than relying on “a patchwork of data partners,” Apple is growing its own map data.
It’s doing this by using first-party data gathered by iPhones with a privacy-first methodology and its own fleet of cars packed with sensors and cameras. The new product will launch in San Francisco and the Bay Area with the next iOS 12 beta and will cover Northern California by fall.
Every version of iOS will get the updated maps eventually, and they will be more responsive to changes in roadways and construction, more visually rich depending on the specific context they’re viewed in and feature more detailed ground cover, foliage, pools, pedestrian pathways and more.
This is nothing less than a full re-set of Maps and it’s been four years in the making, which is when Apple began to develop its new data-gathering systems. Eventually, Apple will no longer rely on third-party data to provide the basis for its maps, which has been one of its major pitfalls from the beginning.
Well worth a read if you’re interested in mobile maps: Panzarino’s article digs down into how Apple will collect and process its mapping data. how it plans to dramatically speed up changes and updates to the map, and how (it says) it’s taking privacy seriously at every step of the process.
Video and presentation slides from Apple’s “Introduction to MapKit JS” session at WWDC yesterday afternoon. MapKit JS is, as I mentioned Tuesday, a method for developers to embed Apple’s maps on their websites. Apple is pitching it as a way for developers who use Apple Maps in their iOS apps to use the same maps on their websites: continuity of look and feel and all that.
MapKit has been around for a few years as an API to allow iOS developers to embed Apple’s maps into their apps. What seems to be new this year is MapKit JS, which enables developers to do with Apple Maps that they’ve been able to do for years with Google Maps, OpenStreetMap, MapBox and even the Ordnance Survey: embed the maps on their websites. Keir Clarke runs through the services and limitations of the API: notably, it requires an Apple Developer account ($99/year) to use. It’s still in beta, so everything is subject to change; in the meantime, Vasile Coțovanu has whipped up a demo. [Maps Mania]
As of iOS 12, coming later this year, CarPlay will support third-party map applications like Google Maps and Waze, Apple announced during its WWDC keynote earlier today: AppleInsider, Engadget, The Verge. Up until now the only maps available via CarPlay were Apple’s own; drivers who would rather use something else—and I know lots of them are out there—will soon have that option.
“We made significant changes to all of our development processes because of it,” says Cue, who now oversees Maps. “To all of us living in Cupertino, the maps for here were pretty darn good. Right? So [the problem] wasn’t obvious to us. We were never able to take it out to a large number of users to get that feedback. Now we do.”
A major feature of Apple’s forthcoming Maps application for OS X 10.9 Mavericks is enhanced error reporting. AppleInsider has the details. This was inevitable, not just because of the uneven quality of Apple’s maps and the reputational firebombing they’ve gotten since their launch last year, but because all online maps suck and need error reporting. Of course, reports are one thing; how quickly and effectively they’re acted on—that’s what’s important.
A Mac version of Apple’s maps was among the new features announced for Mac OS X 10.9 Mavericks at Apple’s Worldwide Developers Conference (WWDC) on Monday. Coverage: 9to5Mac, The Verge. I’m surprised to see that they’re doing it as a standalone application rather than on the Web, which is what I’d expected. One trick of the app is that you can send turn-by-turn directions to your iOS device. There’s an API, so developers will also be able to integrate the maps into their own apps. If they want. Cue old and tired jokes about Apple maps’ quality in three, two …
So last week Google held a press event outlining several upcoming features and innovations in Google Maps, including the ability to use maps offline on Android (i.e., without a network connection), some pretty impressive 3D imagery, and shrinking the Street View camera so that it’ll fit in a backpack. The event was widely seen as a way to grab some of the limelight prior to Apple’s announcement of its own built-in maps for iOS, which came today (more on which in a moment).
There are rumours that for iOS 6, the next version of the operating system for the iPhone, iPad and iPod touch, Apple will replace Google Maps with an in-house mapping application with an impressive 3D mode; the app will apparently “blow your head off,” to quote John Paczkowski’s source. Much is being made of the 3D mapping possibilities, thanks to Apple’s acquisition of C3 Technologies. My interest, and my concern, is with the base mapping data. If this is going to be a flagship product, and signs point to that being the case, Apple can’t use OpenStreetMap (as it does with the iOS iPhoto app), at least not exclusively: it’s still not ready. It would be better, but not cheaper, if Apple used Navteq or Tele Atlas map data directly; when Google abandoned them for their own map data, Google Maps’ quality did not universally improve. (AppleInsider, Daring Fireball, TUAW.)