LiMo Foundation

BONDI is an initiative by the Open Mobile Terminal Platform (OMTP) whose aim is to consistently and securely open up access from web applications to device and network resident capabilities. The BONDI activity is defining the key mobile interfaces which are currently not standardised, but present the best opportunities for developers to provide great mobile web services. These interfaces are then made available through a security framework that can be readily managed to maximise the protection of the user and that can be most applicable to the type of user. The interfaces which have been specified include messaging, location, phone status, gallery, camera, application settings and Personal Information Manager (PIM). By enabling access in a consistent manner to these interfaces, BONDI is providing the developer with the ability to produce new web applications which will be capable of running across different devices and platforms.

LiMo has initiated the LiMo BONDI SDK project in an effort to create an open source SDK that enables development of Web applications and widgets that can run across all mobile handsets that support a BONDI - complaint Web runtime. More information can be found here: http://bondisdk.limofoundation.org

Developers will have 4 possible routes to market:

• Embedded software for the phone makers who are members of LiMo (make or buy decisions)
• 3rd Party applications to be sold to the phone makers for value-add
• 3rd Party applications to be sold to the operators for value-add and integrated by the phone-makers
• 3rd Party applications that can be loaded after market and paid for by the end user; for example, developers can currently distribute their apps through the Vodafone 360 shop.

The LiMo Platform supports C and C++.

Native SDKs are currently available to Members in beta mode while BONDI SDK are available to developers under an open source license on the LiMo BONDI SDK website. The native SDK will be publicly available in the second half of 2010.

There are 5 main reasons why developers should develop for the LiMo Platform:

Scale:

LiMo's membership includes support and participation of 11 global mobile operators, who collectively represent a subscriber base of nearly 1 billion mobile subscribers worldwide. LiMo's OEM membes ship nearly half a billion handsets each year.

Choice:

With the LiMo Platform, you will be able to choose between different environments for realising you mobile vision. You can either develop natively or for a broad range of runtimes that are supported by the LiMo Platform and in LiMo compliant handsets - Native, Web and Flash (coming soon).

Lineage:

The LiMo Plaform is based on Linux; so if you are familiar with native Linux development, LiMo presents a very natural opportunity to transfer these skills into the mobile marketplace.

Future Proof:

The LiMo Platform is dynamic and constantly evolving to incorporate the latest technology. It benefits from the strong support of major stakeholders in the industry, who are leveraging the LiMo Platform to realise their service strategy.

Use of Open Source:

The LiMo Platform pragmatically blends open source with proprietary development methodologies. Learn more on LiMo's open source site at http://opensource.limofoundation.org

The R3 Platform features support for advanced Location Based Services (LBS) and contact management and extends existing features within the R2 Platform such as support for application management, advanced UI and multimedia technologies, and enhanced security and networking.

The LiMo Foundation code base is contributed by members and integrated under the supervision of the Architecture Council and its working groups. Members contributing code and IP have a variety of licensing options - an overview of which is outlined in the LiMo Foundation IPR Guide, which can be downloaded from the LiMo Foundation website. The full Intellectual Property Policy of LiMo Foundation, which governs contributions, can also be downloaded from the LiMo Foundation website.

The Common Code comprises the architecture modules that have been approved by the Architecture Council for inclusion in the Foundation Platform and that are required to be part of every Foundation-certified device.  The Non-Common Code comprises modules that have been approved by the Architecture Council for inclusion in the Foundation Platform but that are not required to be included in an implementation of the Foundation Platform in order for such implementation to be compliant with Foundation specifications.

In practice, Common Code will include functionality that will be required in the majority of implementations, while Non-Common Code may include device, geography, or application-specific functionality. 

R3 devices are expected to come to market in the second half of 2010. The flagship Vodafone 360 H1 and 360 M1, manufactured by Samsung are currently shipping in most European markets.

More than 50 LiMo handset models have shipped to date in various parts of the world. A broad range of devices based on the R3 release of the LiMo platform are expected to reach the market in the second half of 2010.

The market's desire for mobile Linux devices spans borders and device types - LiMo's platform will be suitable for mass-market phones as well as feature phones. LiMo handsets are already available in several countries worldwide.