Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Eric Zeman

Google Debates Fate Of Motorola Smartphone Business

Google is giving mixed signals about its plans for Motorola's hardware once acquisition is complete. The safest best: Stick with the patents and forget about making the phones.

After spending several weeks probing Google and Motorola for clues as to what the companies will do once Google finalizes its acquisition of Motorola, The Wall Street Journal's Dennis Berman concludes that the answer is, well, inconclusive. Neither company is really sure how things are going to work out, at least with respect to Motorola's smartphone business, once Google owns the ailing phone maker.

There are thorny and nettlesome issues at hand that can have a major impact on the Android ecosystem if things run unchecked.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Google announced its intent to acquire Motorola for $12.5 billion last August. The deal has won regulatory approval in the U.S. and in Europe, but has been dealt a delay by Chinese regulators. Even so, Google expects to close the deal during the first half of 2012.

[ For more analysis, see Google's Motorola Mobility Buy: Patent Power Shift. ]

From the outset, Google was open about why it wanted to buy Motorola: Google needs Motorola's 17,500 phone-related patents to protect itself from intellectual property-related lawsuits from competitors such as Apple and Microsoft.

Great, that makes sense, but it still leaves to question what Google will do with Motorola's world-spanning design and manufacturing facilities, not to mention its 20,000 employees. Does Google really want to be a company that makes actual, physical goods, or would it rather remain in the virtual realm?

The sticking point is that Google is the creator, distributor, and guardian of Android. Android is its wildly popular smartphone platform. Google gives away the base code of Android for free, and in return is allowed to install its goods and services on smartphones. Those smartphones, however, are manufactured by some 55 different companies, including Samsung, HTC, Sony Mobile, LG, Asus, and myriad others.

Can Google effectively keep its Android software business (which companies have staked their own fortunes on) and its former-Motorola handset businesses separate entities? Google's Andy Rubin has insisted that will be the case. Rubin said earlier this year that Google will institute a "firewall' between its Android and Motorola teams so there is no conflict of interest when it comes time for Google to provide code to other hardware makers.

Google can't afford to tick off its hardware partners. With 850,000 Android handsets being activated daily around the world, it risks a huge opportunity if the ecosystem collapses. Even if Google can make its own Android smartphones via Motorola, it could never make up for the losses that would occur if other OEMs gave up on Android.

According to Berman, reports in Asia suggest that Motorola might divest Motorola's handset business and simply hold onto the patents. Huawei is said to be one of the companies interested in Motorola's hardware, but a source close to Google told Berman it will never play out that way.

Berman's conclusion is disquieting. "There's only a cocky belief that Google really can be all things at once: a hardware company with software margins, and a neutral Android arms dealer that just happens to be building its own Motorola army on the side," he wrote.

I'd bet money that Google's hardware partners aren't so sure, and are waiting to see how it proceeds with the hardware business once the acquisition is complete.

See the future of business technology at Interop Las Vegas, May 6-10. It's the best place to learn how cloud computing, mobile, video, virtualization, and other key technologies work together to drive business. Register today with priority code CPQCNL07 to get a free Expo Pass or to save 25% on Flex and Conference passes..



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.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.