Big Data. Big Decisions
InformationWeek
Special Coverage Series


The Google Phone That Never Was

Evidence at the Oracle v. Google trial reveals what the original Google Phone prototype looked like, before Apple's iPhone moved the goal posts. Related Android revenue information is also enlightening.

The Google Phone, as the company's Android phone prototype was called in November 2006, looks primitive by today's standards, but it was competitive at the time. The $199 device was to have run on T-Mobile's network and featured a $10 per month unlimited data plan for Internet browsing, Gmail, and messaging.

Trial Exhibit 387: Industrial Design Concept

The phone was expected to include a 200MHz or better ARM 9 chip, with GSM EGPRS baseband or possibly WCDMA. The design called for at least 64MB RAM and 64MB ROM, with external storage, a 16-bit color or better QVGA TFT LCD display, navigation keys, a 2MP CMOS camera, USB interface and Bluetooth 1.2 or 2.0.

Then Apple unveiled its iPhone on January 9, 2007 and it was back to the drawing board. The result was the T-Mobile G1, introduced in October 2008.

[ What does Apple have up its sleeve next? See Apple iOS 6 Wishlist: 10 Features We Want. ]

The Google Phone that never was showed up as evidence in Oracle's copyright and patent infringement lawsuit against Google. Oracle claims that Google copied its proprietary Java APIs to create Android. Google has admitted that a few lines of the Java APIs are present in Android but it insists any copying that occurred was a mistake, is trivial, and is defensible as fair use. Google further asserts that APIs aren't subject to copyright.

The Oracle v. Google trial continued on Thursday, with former Sun CEOs Jonathan Schwartz and Scott McNealy each taking a turn on the witness stand. Schwartz's testimony generally supported Google's arguments and McNealy's generally supported Oracle's.

The evidence obtained by Oracle via legal discovery and entered into the court record confirms that Google has struggled to match the Apple's iOS results with Android. For example, Google in 2010 predicted that its 5% share of Android app revenue in 2011 would come to $14.5 million. That would put the total app revenue projection for the year at $290 million, of which 70% or $203 million would go to Android developers. During 2011, Apple paid its developers about $2 billion.

Google's expectations about the ratio of paid apps to free apps downloaded by Android users is striking: While it's widely known that a greater number of the apps downloaded by Android users are free compared to the apps downloaded by iOS users, what's surprising is that Google expects a mere 1% of Android apps to be paid. A report last year suggested that 88% of gaming apps downloaded on iOS are free, which would make 12% paid. Google's internal projections from 2010 expected 99% of Android app downloads to be free in 2012, noting that this "conservative estimate" of 1% paid apps was far from Apple's 25% paid app figure.

But the documents also show that Android is a source of real revenue for Google. The company projected it would make $240.3 million on Android in 2010 and $840.2 million in 2012. Google believed it could make at least $1.3 billion in gross revenue from Android in 2013, or $800 million in net revenue, and possibly much more.

In fact, Android has been exceeding Google's expectations in terms of adoption. In mid-2010, the company expected there would be 145 million Android phones activated by the end of 2011. In Q3 2011, Google reported that over 190 million Android phones had been activated. By the end of 2011, Asymco estimated that between 224 and 253 million Android devices had been activated.

With that kind of growth, it's hardly surprising that Oracle came knocking with its hand out.



Related Reading


More Insights




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.