Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Mobile

Analysis: How Smartphone Platforms Compare


A group of leading cellular carriers and equipment makers--NTT DoCoMo, NEC, Motorola, Panasonic, Samsung, and Vodafone--is developing its own mobile Linux, planned for release this year.

NTT DoCoMo, the driving force behind the partnership, and other carriers are pursuing a dual-sourcing strategy, as they don't want to depend on one operating system, and customers like choice. Symbian is the other operating system they've settled on.

Since some members are competitors, however, the consortium faces challenges around governance and sharing of intellectual property. In order for the initiative to succeed, the companies will have to develop APIs that support applications across devices. NTT DoCoMo and the handset makers plan to form an independent foundation to jointly develop APIs, architecture specs, reference source code, and tools.

One of the goals of the LiPS Forum is to develop standard APIs for services such as messaging, presence, and voice calling, as well as APIs for application and device management. LiPS plans to publish the service layer APIs this year. Access, meanwhile, plans to open source its application framework

for the Access Linux Platform, and it's working with LiPS Forum and the Open Source Development Labs to determine how they may adopt the framework.

What all this means is that the existing Linux and Palm smartphone camps may begin to gravitate toward two emerging Linux options. But even that may be too many. After all, there's only one BlackBerry OS, one Symbian, one Mac OS X, one Windows Mobile.

Linux's challenge: reducing the fragmentation.


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

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's 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 or spam. Dr. Dobb's 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.