Commentary

Mobile Linux Gets Another Shot In The Arm

There's some good news for the development of mobile Linux lately. Today, Access was tapped to develop a Linux platform for NTT DoCoMo. Yesterday, the Linux Phone Standards Forum agreed to its first specification for mobile Linux. These announcements come just weeks after Google drops word of its Linux-based Android platform. Mobile Linux is gaining steam.

There's some good news for the development of mobile Linux lately. Today, Access was tapped to develop a Linux platform for NTT DoCoMo. Yesterday, the Linux Phone Standards Forum agreed to its first specification for mobile Linux. These announcements come just weeks after Google drops word of its Linux-based Android platform. Mobile Linux is gaining steam.Each one of these bits of news raises the positive outlook for mobile Linux. Here's a snapshot of why they are important for the mobile industry.

Access has been working on a next-generation, Linux-based OS for Palm devices for a while now, though it's been slower to get off the ground than many have hoped. The demos on the Access site are pretty cool. That NTT DoCoMo (the largest cell phone network operator in Japan) has placed its faith in Access' Linux platform is telling. Access also has the backing of hardware manufacturers NEC and Panasonic.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The company said this in a press release:

Access will make use of MOAP(L) (Mobile Oriented Application Platform based on Linux) which is the FOMA mobile platform used by NTT DoCoMo, and will lead the development of a shared software platform that also conforms to specifications of the LiMo Foundation, an independent, non-profit foundation established with the aim of promoting the use of Linux by the mobile industry. The five companies have also agreed to consider development of an operator pack for NTT DoCoMo based on the shared platform. Access intends to begin marketing the commercial products resulting from these efforts during fiscal 2009.

"Linux-based mobile phones are attracting attention at home and abroad," said Toru Arakawa, president and CEO, ACCESS. "The agreement by NTT DoCoMo, NEC, Panasonic Mobile and Esteemo to join us in discussing the development of a shared Linux-based platform and operator pack will contribute to the efficient development and prompt release of next-generation handsets by providing the type of user-friendly interface that is only possible with Linux."

I agree with Mr. Arakawa.

That news doesn't outshine LiPS' announcement, though. LiPS hopes to publish actual standards, rather than just code, that govern the development of mobile Linux. Yesterday it said that it has agreed to the first set of APIs for mobile Linux developers. The APIs cover mobile calendar, messaging, presence, reference model, telephony, and user interface services.

LiPS Forum President Haila Wang said, "LiPS is following the clear path blazed by GSM, TCP/IP, WiFi, and other standards that enable communications among device types and brands, over multiple operator networks, and across regional markets."

Having agreed-upon standards that organizations can rely on and follow is important. This is a big first step in granting mobile Linux a more uniform future. LiPS also said that it will work on creating more standards in 2008, specifically the application framework, advanced services APIs, device management APIs, and additional enabler APIs (e.g., for multimedia).

These two announcements in tandem with Google's plans for mobile Linux paint a positive picture for the open platform. The broad alliance of 30+ companies supporting Android shows that there is definitely faith in what Linux has to offer mobility. It looks like 2008 is going to be a big year for Linux.


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