Commentary

Sony Ericsson: Yeah, We're Going To Wait For Android 2.0

Sony Ericsson may have joined the Open Handset Alliance, but it appears as though the company -- known for its music- and camera-centric mobile phones -- doesn't quite have faith in Android 1.0 or 1.5. It is going to wait for Android 2.0 before it brings any Android handsets to market.

Sony Ericsson may have joined the Open Handset Alliance, but it appears as though the company -- known for its music- and camera-centric mobile phones -- doesn't quite have faith in Android 1.0 or 1.5. It is going to wait for Android 2.0 before it brings any Android handsets to market.According to DigiTimes, Peter Ang, vice president of marketing, Asia Pacific at Sony Ericsson, recently said, "The Android 2.0 will have more multimedia support that the previous Android OS." That's a key area for Sony Ericsson to be concerned about.

Many of Sony Ericsson's higher-end phones fall in to one of two categories: The Walkman range or the CyberShot range. I'll give you two guesses as to what user demographics those two series target.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

With such a key emphasis on multimedia capabilities, it is little wonder that Sony Ericsson would consider holding off until a more robust version of Android is available with better media capabilities.

Let's face it, the current iteration of Android is not setting the music-listening and picture-taking crowds on fire. Some of the major upgrades from Android 1.0 to Android 1.5 include better multimedia features, but they are still behind some of the competition.

Ang also said that the company will continue to support the Windows Mobile and Symbian platforms.


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