Home
Eric Zeman

Eric Zeman



Why Apple Can't Deny Google Maps On iPhone

Comments | Eric Zeman, InformationWeek | November 16, 2012 01:41 PM


Apple iOS 6: 10 Most Interesting Features
Apple iOS 6: 10 Most Interesting Features
(click image for larger view and for slideshow)
Google has nearly completed work on a new version of Google Maps for the iPhone. Citing sources familiar with Google's plans, The Wall Street Journal reported that Google is now field testing the app outside of Google. It should soon be ready for Google to submit to Apple for approval.

Apple booted Google Maps from the iPhone, iPad and iPod Touch earlier this year with the introduction of iOS 6. Google Maps was a part of iOS from the very first iPhone through September of this year -- a partnership that lasted more than five years. But Apple has been divorcing itself from Google's goods and services ever since the two began battling head-to-head with competing smartphone platforms.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Apple replaced Google Maps with its own mapping product. Embarrassingly for Apple, Apple Maps has been a complete failure. Users immediately complained that the app was inferior to Google Maps. It was (still is?) riddled with mistakes, missing towns, distorted imagery, and other goof-ups. The black eye Apple received for Apple Maps probably played a role in Apple iOS head Scott Forstall's recent departure from Apple. Apple was forced to apologize for the Apple Maps disaster and has been working hard to fix the software ever since.

What everyone wants to know, of course, is whether or not Apple will approve the new Google Maps.

[ For more on the status of Google Maps for iOS 6, see Google Maps For iOS 6 In Beta. ]

Traditionally, Apple has disliked apps and services that compete with the iPhone's (or iPad's) native software and services. For years, it wouldn't allow competitive apps in the app store. It has relaxed that policy a bit. For example, iPhone users can use alternate email applications (including Google's Gmail app), alternate browsers (including Google's Chrome app), and alternate cloud syncing services (including Google's Drive app).

After the Apple Maps fiasco, Apple understood that it had made a mistake. It recommended that iPad and iPhone users find an alternate mapping application. In fact, the iTunes App Store still has a place reserved on the home page that takes users to a collection of mapping and navigation apps. Some of the apps listed there belong to MapQuest, TomTom, Magellan, TeleNav, Garmin, and even Microsoft. All these companies offer navigation apps that compete with Apple Maps. Some are free and some are not, and many don't have the deep system-wide integration that Apple Maps does (or that Google Maps did), but they still help iPhone users get from Point A to Point B and show them nearby points of interest.

Considering how Apple has relaxed some of its traditional app policies and is currently recommending competitors' mapping apps, it would look petulant and hypocritical if it were to deny Google Maps for the iPhone. Apple may not typically concern itself over such things, but this is a major exception. Denying Google Maps at this point would be opposite of everything Apple is already doing. It would be an obvious move against a competitor. It would make Apple look petty and pathetic in the eyes of many.

Apple can't say no.

InformationWeek is conducting a survey on the state of Apple in the enterprise: How has the flood of iOS devices affected use and support of Apple systems? If you're not supporting Apple gear, what's holding you back? Take our InformationWeek Apple Outlook Survey now. Survey ends Nov. 26.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events