Commentary

Ed Hansberry
 

Google Branded Phone Rumored in 2010

Ever since Google's Android phone has been known about, there has been speculation that Google would make a "Google Phone" to sell. Google has steadfastly maintained they don't want anything to do with hardware though. They are satisfied with making the platform and working with hardware makers to bring Android to the consumers. That may change.

Ever since Google's Android phone has been known about, there has been speculation that Google would make a "Google Phone" to sell. Google has steadfastly maintained they don't want anything to do with hardware though. They are satisfied with making the platform and working with hardware makers to bring Android to the consumers. That may change.eWeek is reporting that an analyst is predicting in 2010, Google will launch their own phone with Android, and it would run Flan, an as yet unreleased version of Android. Android builds take the names of deserts or sweets found in a bakery, and are released alphabetically. Eclair is Android 2.0. Flan might be 3.0 or minor update in the 2.x range.

The article cites that this might upset carriers if Google sells the device directly to consumers. I don't think that will be a huge problem. If Google did, there would be no subsidy and people in the US just aren't used to paying $300-$600 for an unlocked device. I think it is more likely that Google would work with carriers to sell the device, even if they sold some devices direct.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Overall, I think this is a good idea. One of the complaints I am starting to see about phones running Android is the market is beginning to fragment. With a dozen hardware makers each putting their own spin on the platform, combined with a myriad of hardware configurations, it is getting difficult for developers to make their software easily work on all of the devices, and that is a recipe for disaster. If Google showed the world their vision of what an Android phone should be like, it could make life easier for developers and users. Competing hardware makers might try even harder to make their devices unique, but once consumers wised up to the fact that many apps may not work on such a device and therefore passed on it, the makers would be more diligent in making sure their phones fit the standard.

Worst case scenario Google's hardware partners left the platform for another. Google has the branding to make it work on their own. Microsoft did the same thing when it came out with the Zune. The previous Windows Media Player and Plays For Sure model did nothing against the iPod. The Zune quickly surpassed other MP3 players and while it still trails far behind the iPod, it is more successful than any previous Microsoft powered player.

Speaking of Microsoft, they too should consider building a Windows Phone, integrated with Zune bits for media. While there are some nice phones out today running Windows Mobile, none are really making a dent against the iPhone. The Windows Phone brand has become so muddled under hardware maker's customizations that many WinMo users have no clue that they actually have a Windows Phone.

In watching this, Google has the benefit of 20/20 hindsight and, if the rumors are true, are heading the problems off early on in Android's life.


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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links