The MeeGo Project -- the open source project which merges Intel's Moblin project and Nokia's Maemo into a single Linux distribution -- has announced "Day 1" of its MeeGo Handset User Experience Project, making the handset baseline source code is available to the development community. This code is being actively developed as MeeGo 1.1, which is scheduled for release in Q4 2010.
Handset-specific source code currently under development toward the MeeGo 1.1 for Handsets release will be opened to the developer community to access, contribute to and participate in. This move marks the first MeeGo code supporting a touch environment. The MeeGo Handset Day 1 code is primarily targeted at platform developers, handset vendors and operators and is available for immediate access from meego.com -- interested developers can preview the code and try it out using Aava Mobile or the Nokia N900 as development reference hardware.
MeeGo Gitorious provides all the sources and infrastructure to perform the weekly builds for MeeGo 1.1 development. The MeeGo UI team has also been creating the handset reference user experience and preparing the MeeGo UI design principles and interaction guidelines. This milestone marks the completion of the merger of Moblin and Maemo as major architecture decisions and technical selections have been determined. MeeGo is also opening the MeeGo Build Infrastructure.
The MeeGo Project Handset Day 1 includes:
- MeeGo APIs, incorporating Qt and MeeGo Touch UI Framework (MTF)
- Subset of the handset reference UI and applications
- Status Bar: clock, network, Bluetooth, 3G connection, notifications, and battery charge
- Home Screen
- Lock Screen
- Application Launcher
- Virtual Keyboard
- Applications: Dialer, SMS, Browser, Contacts, and Photo Viewer
- MeeGo Core OS (including the middleware components)
- Hardware adaptation support for Intel Atom-based handset (Moorestown) and ARM-based Nokia N900
The MeeGo Handset Day 1 image is provided as a community developer preview and we are in a very early and active development state. While we don't recommend installing it on your primary phone just yet, we invite all developers who are interested to have an early look using a development device.
