I’m surprised that Intel have been allowed to announce partner names but in a presentation at the Barclays Capital 2010 Global Technology Conference, Paul Otellini has done just that and highlighted that Windows, MeeGo and Android will be on Atom next year.

The report comes via CNet who tracked the live audio from the conference and picked up that the Android builds will be both Froyo and Gingerbread. He also highlighted that Oaktrail is the Windows-compatible version of the new platform and Moorestown optimised even further and supporting only MeeGo and Android. That much we knew already. We also know from previous information that smartphones on Moorestown are taking longer than planned. Behind the scenes, I’m getting the feeling that Moorestown won’t be used for phones and that the focus is now on Medfield, due in late 2011. Note also that the Android build is behind MeeGo. That’s information that we were given at IDF in Sept 2010 and it means that those devices could be planned for the second half.

Slightly disappointing is that the slide shows only Tablets and that the bulk of these are Windows. Some of those won’t even be on the mobile platform because the netbook platform is going to feature. Focus should really be on unique designs such as smart-books, social netbooks and how about a bit of keyboard love? Continuing use of Windows with its lack of ‘always-on’ and business focus is just going to end up with devices that get bad reviews.

Highlight for me is Dell using Android. This will be on Moorestown and could be their 10 inch offering. If so, that’s a great win for Intel.

The good news here is that Moorestown is ready. I heard only last week that it’s been in production for months now. It only needs the OS to be completed and we’re away with a new always-on option and the first X86 platform that doesn’t support a Microsoft OS! I just hope that those MeeGo devices are going to be ground-breaking otherwise Nokia will NOT be happy!

Via Netbook News

During a snowy week in Europe I travelled to London and Berlin to moderate the the AppLab events being run by Intel. I learnt more about the strategy and details but also got some interesting feedback and feelings from the atendees. For those of you not up-to-date with the Intel AppUp Developer Program (IADP) let me try to explain I’ve got time; A 5hr journey back from Berlin to Bonn! Skip the first section if you know the history.

The story so far…

Intel have a strategy (a ‘continuum’ in their words) of mobile and embedded platforms based on the Atom CPU core that stretches way into the future. The new generation of Atom-based platforms start to move away from the traditional PC architecture in order to gain a foothold in the ‘always-on’ category of devices. Unfortunately, there isn’t a Microsoft OS product that works well with these platforms (a first for Intel?) so Intel have teamed with Nokia to build an open-source Linux core that if focused on mobility and fits with both Intel and ARM platforms. That OS is called MeeGo and it is under the care of the Linux Foundation. Meego implements a user interface layer using the Qt product that Nokia own. The Symbian Foundation also use this in Symbian. A basic application suite is being built along with reference UI models.In order to compete with similar mobile products, Intel is also building an application store framework with monetisation possibilities. Finally, there’s a marketing program aimed at seeding the applications. That’s the Intel AppUp developer program. Phew!

Intel Atom platform + MeeGo core + Qt layer + Apps + Appup monetisation for new apps + pot of gold to stimulate the whole stack.

MeeGo is clearly critical for Intel. It’s also critical for Nokia. They are public in saying that next generation smartphones, high-end products, will be based on Nokia. It scares me to think of the amount of money that is on the table here. It’s also interesting to note that AppUp is already available for Windows and targeted at netbooks, a category that is merging with laptops and getting less and less attention as time goes on. Marketing efforts for AppUp and MeeGo have just kicked off with the MeeGo Portal on the AppUp website.

What is AppLab?

We’ve seen The Intel Elements AppUp event in San Francisco (Sept. Report here) and the first joint effort for MeeGo in the MeeGo conference in November.  Both were very big events. On a smaller scale, Intel’s regional offices are running their own programs in order to grow local developer interest and to make connections with ISV’s and finally, we get to AppLab, the events run by the Europe, Middle-East and Africa team (EMEA) who seem to be leading the local effort.

If you’re a developer interested in MeeGo and Intel’s new mobile platforms and opportunities, you definitely need to keep an eye out for events in your country. They are small, well-focused and bring some of the senior members of the teams to you. If you’re not interested in Atom, MeeGo and AppUp, then all I can say is that you need to keep an eye on it!

As you’d expect the events expand on what I’ve just summarised and go deep into explaining the MeeGo architecture, how AppUp works, what tools to use and what the platforms will be able to offer in terms of products.  See below for links to the slides and a video stream.

London.

A slightly busy exhibition of mobile applications in London (Apps World, Olympia) meant that the crowd was largely transient although it was good to see a core of a bout 30 people stay and listen to the whole 4 hours of talks. The crowd were from various parts of the UK with about 30% developers and 30% marketing people. Presentation detail was good but speakers should definitely aim to pep-up and tidy-up their presentations. To be honest, as the moderator, there’s room for me to do the same! This is a critical product for Intel and that impression didn’t come across despite the obvious excitement from the speakers when in a one-to-one chat. Intel should also aim to bind the community together under some sort of interest group created for each event. With many people coming from London it makes sense to sponsor user-group meetings.

Berlin

The mood and setup was convivial, the church-hall location surprisingly well set-up. The sessions and speakers went from top to bottom and as deep as was needed and the small number of local people (about 25 at the Berlin event due to some terrible Europe-wide weather in the days running up to the event) helped to create a real atmosphere of community that should aim to keep connected in Berlin. The specialists brought across their subjects well although again, a measure of excitement needs to be injected. For those in Berlin that are interested in connecting to other users, check out Mobile Freidae, an independent website and community that has already held MeeGo get-togethers.

Use Local MeeGo Networks as connectors?

MeeGo, AppUp, IADP and the related products are new, interesting opportunities and Intel/Nokia really need the word to be spread. If you’re interested in setting up a local MeeGo interest group and covering AppUp, see the MeeGo Wiki.

New News

These events aren’t meant for major announcements but if you listen carefully, you can pick up a few hints.

• The IADP team is going to LeWeb in Paris, France this week. There was also a mention of new languages for AppUp. Add the two together for the answer!
• The MeeGo SDK is coming for Mac-based development to add to Linux and Windows-based environments.
• There’s a desire to make some of the (expensive) software tools low-cost or free for MeeGo devs. The Intel tools (compiler, libraries etc.) are very Atom and power-focussed. If this happens it’s a major advantage for Intel/MeeGo developers.
• I’m getting the feeling that AppUp for MeeGo is coming in Q1 2010. Certainly the marketing is ramping up already.
• There’s lots of prizes, support and free marketing available for early developers. More coming in 2011 (Bigger, apparently.)
• Dixons/Currys/PC World in the UK are ready to push a AppUp on their products; Right up into Laptops.

Is MeeGo the catalyst?

One thing that was easy to spot at the events was the interest in MeeGo. It’s not difficult to see why because the ecosystem for Windows is already mature and splintered. MeeGo is connected with a new, clear and mobile strategy. It’s new too which means there’s an excitement about being first. As we go into 2011, I expect the MeeGo/AppUp story to converge although it will be interesting to see how Nokia markets MeeGo/OVI. In theory, Qt provides a way to write an app and put it across both platforms but that message hasn’t really gone out yet and will be quite the marketing challenge as both sides look to promote their own developer opportunities. Will Windows+MeeGo be bigger than Symbian+MeeGo?

More events planned? MeeGo Roadshow!

I asked Stefan Englet, segment manager for EMEA at Intel about future Intel AppLab events…

We will continue doing “AppLabs” to give developers a full overview of the Intel AppUp Developer Program, the support they [can receive] and the opportunities for monetizing their applications. Additionally we will set up a MeeGo road show through central Europe, providing the latest about the cool new mobile OS – stay tuned, planned for 2nd quarter 2011.

The AppUp team is at LeWeb this week. Keep an eye out for Scot Appland and Peter Biddle, both senior members of the core AppUp team.

As for global activities, we’ll have a chance to catch up with the AppUp teams at CES in January so stay tuned here for more.

You can also check out this forum on the Intel Software Network for more event information.

All presentations from the event (PDF)

• Marketing overview
• MeeGo overview
• AppUp SDK details
• AppUp Validation process
• Intel optimisation tools

More information.

• End-user applications site: AppUp.com
• Developers should start here
• MeeGo / AppUp Portal is here and contains links to all the tools.
• AppUp forums at the Intel Software Network
• There’s also a site, MeeGo.com/Developers for the MeeGo-focused
• Video streams from the event are here and here. (Low-Q recordings of the live stream)

The AppLab events were fun and educational and really underline the importance of these products for Intel. Next update is expected in just four weeks at CES, Las Vegas.

It’s hard to believe that the iPhone launched without an application store but it did. If you’ve lived with ‘apps’ for any length of time you’ll appreciate the advantages and probably won’t want to go back to a place without an integrated app store right?

• Discovery
• Try-and-Buy
• Unified Billing
• Discussion / Comment / Sharing
• Developer opportunity (money, fame!)
• Diversity / Niche applications
• Device Customisation
• Application control and conformity
• Centralised security checks
• One-stop-shop
• Competition / Comparison of similar applications
• 3rd-party Curation

Yes, apps have been around for a long time but the app store brings many important advantages. It’s big business.

Wipconnector now lists over 100 app stores and in the latest report (PDF) asks the question – “How Many App Stores is Too Many. inch It’s almost the same question as “How Many Blogs is Too Many? inch and we all know that there’s enough desire, demand and advertising out there to drive a scary number. My prediction is that the number of store ‘fronts’ will continue to rise but we might see consolidation on the back end. API’s, SDK’s and submission processes that align and then offer multiple store fronts (based on device type, software brand or genre) seem the perfect solution to applications stores with huge numbers of apps. Actually, blogs and app store fronts could link up very well with blogs driving the SEO and readership to a niche audience and then offering a tailored application store with reviews and a percentage of revenue. It’s certainly something I want to do in the mobile computing niche when possible.

Maybe I’ll have a different view at the end of next week though as I expect to learn a lot more at two Intel-sponsored sessions. The first is App World at Olympia in London. On the 1st Dec (Wednesday) I’ll be hosting a 4-hour session where Intel representatives will talk about the Intel AppUp Developer Program, the AppUp store for Windows and MeeGo, the opportunities and software engineers will be present to help developers get started.

“We’ll be discussing revenue opportunities for Adobe AIR* and Windows* C/C++ developers, as well as how you can optimise existing iOS, Windows and runtime applications for netbooks. inch

I’ll be around for the day so if you’re at the event, drop by and say hi!

After App World I’ll be flying over to Berlin for the Intel App Lab to practice my ‘Denglisch.’  Again, I’m introducing speakers at the event and looking forward to meeting people in what has to be one of the hottest cities in Europe for new media software and services.

“Hear why you should develop for the Intel AppUpSM center, learn about the monetization opportunities, see live coding demonstrations and talk to Intel experts in our staffed hands on training session. Bring your code and questions! inch

You can find information and register here. The event is free and there’s a chance to win a netbook along with other prizes. Beer, pizza and chat after the event too!

See you there.
Chippy

It’s hard to believe that the iPhone launched without an application store but it did. If you’ve lived with ‘apps’ for any length of time you’ll appreciate the advantages and probably won’t want to go back to a place without an integrated app store right?

• Discovery
• Try-and-Buy
• Unified Billing
• Discussion / Comment / Sharing
• Developer opportunity (money, fame!)
• Diversity / Niche applications
• Device Customisation
• Application control and conformity
• Centralised security checks
• One-stop-shop
• Competition / Comparison of similar applications
• 3rd-party Curation

Yes, apps have been around for a long time but the app store brings many important advantages. It’s big business.

Wipconnector now lists over 100 app stores and in the latest report (PDF) asks the question – “How Many App Stores is Too Many. inch It’s almost the same question as “How Many Blogs is Too Many? inch and we all know that there’s enough desire, demand and advertising out there to drive a scary number. My prediction is that the number of store ‘fronts’ will continue to rise but we might see consolidation on the back end. API’s, SDK’s and submission processes that align and then offer multiple store fronts (based on device type, software brand or genre) seem the perfect solution to applications stores with huge numbers of apps. Actually, blogs and app store fronts could link up very well with blogs driving the SEO and readership to a niche audience and then offering a tailored application store with reviews and a percentage of revenue. It’s certainly something I want to do in the mobile computing niche when possible.

Maybe I’ll have a different view at the end of next week though as I expect to learn a lot more at two Intel-sponsored sessions. The first is App World at Olympia in London. On the 1st Dec (Wednesday) I’ll be hosting a 4-hour session where Intel representatives will talk about the Intel AppUp Developer Program, the AppUp store for Windows and MeeGo, the opportunities and software engineers will be present to help developers get started.

“We’ll be discussing revenue opportunities for Adobe AIR* and Windows* C/C++ developers, as well as how you can optimise existing iOS, Windows and runtime applications for netbooks. inch

I’ll be around for the day so if you’re at the event, drop by and say hi!

After App World I’ll be flying over to Berlin for the Intel App Lab to practice my ‘Denglisch.’  Again, I’m introducing speakers at the event and looking forward to meeting people in what has to be one of the hottest cities in Europe for new media software and services.

“Hear why you should develop for the Intel AppUpSM center, learn about the monetization opportunities, see live coding demonstrations and talk to Intel experts in our staffed hands on training session. Bring your code and questions! inch

You can find information and register here. The event is free and there’s a chance to win a netbook along with other prizes. Beer, pizza and chat after the event too!

See you there.
Chippy

Moorestown is late. There’s no way that Intel can spin it otherwise because I’ve asked officials many times and they always promised ‘products’ in 2010. All we’re hearing about is Oaktrail and the reason for that might be because there isn’t an operating system for Moorestown yet. Moblin, MeeGo and Android are all listed as supported operating systems but none of those builds are completely ready for X86 prime-time yet. It looks like Moorestown is sitting in the wings for the time being and that’s very disappointing.

While we wait, let’s remind ourselves of some of the platform characteristics.

Moorestown is  a mobile-focused platform that uses an Intel Z6xx CPU where the memory bus, display controller and graphics (3D and video) are on the main die Lincroft is the codename of the CPU. There’s no BIOS, no ACPI and no real PCI bus on the controller chip (Langwell) and therefore no Windows 7 support. The platform is designed to work with a special power control chip called Brierstown which provides the ‘power island’ support which will be critical in improving battery life and, for the first time, allowing an always-on idle mode that can be used for smartphones. It also integrates tightly with the Intel wireless module called Evans Peak.

Oaktrail is similar (but includes components to allow it to support Windows) as is Tunnel Creek. Tunnel Creek (E6xx CPUs) is intended for embedded designs but contains the same graphics core as Moorestown and Oaktrail. With 2x the 3D performance of the older Menlow platform  and a 20Mbps-capable hardware video decoder and 720p encoder, all based on PowerVR technology, it’s interesting to think about performance in terms of a handheld device.

Have a read at the Intel Embedded site here.

Although I didn’t know this at the time, it turns out that Antix is quite the multi-OS gaming platform. It’s a solution that allows purchase, play, sharing and trial of games between people and different devices running different OS’ (More here.) At the MeeGo conference last week I caught up with Costas Stylianou of Intel’s AppUp team who was demonstrating a multiplayer game.
While the game demo might be interesting, I think it’s more interesting to see Intel demonstrating a gaming platform thats is being ported to AppUp.

The demo is being done on a MeeGo TV platform and a MeeGo Tablet – the WeTab.

I’m looking forward to a multiplayer game of Raging Thunder with another netbook owner soon but watch out, it seems like I was able to play while holding a camera and interviewing Costas!

Just a few days after the first ever MeeGo conference I have the best chance ever to take what I’ve seen, heard and learnt to try and predict when and what will happen with MeeGo in 2011. When will versions ship? On what hardware? When will the applications store ship and finally, when will end-products ship both via Intel and Nokia funding and, importantly, through independent vendors.

First let’s remember that MeeGo is an offering to developers, OEMs, manufacturers and other non-end-user customers. Like Android open-source, it will comprise a complete core, a vanilla user interface and a basic set of core applications. Driver support will be limited to common open-source drivers, codecs for audio and video will be limited to free versions and there will be no applications store. While ‘hacker’ types may welcome the new OS, end-users are unlikely to be too thrilled. Journalists that don’t get the whole picture are likely to react with negative reports. Once again, remember that MeeGo on end products will be different to what you see coming out of the MeeGo project.

Let’s also remember what MeeGo is about. It’s an open-source project run by the Linux Foundation and funded by Intel and Nokia for a range of products from mobile phones, in-vehicle entertainment, TV, netbooks, ‘smart’ books and tablets. Intel need MeeGo for their new low-power platforms (Moorestown and Medfield, the handheld platforms, just won’t work without MeeGo although Android is also in the works for these platforms) and Nokia have committed to bringing their next flagship product out with MeeGo. The stakes are very very high for both companies. MeeGo will happen, products on MeeGo will happen and applications on products on MeeGo will happen. But when?

It is possible to get a product out using MeeGo today. The WeTab proves it’s possible but there’s a list of things that need to happen before ‘milestone’ products appear. I also refer to these products as ‘disruptive’ because they will be good enough to compete in the same space as the best-of-breed in their category. There’s also another category of important products and that is those that are not funded by the MeeGo partners. Here’s what needs to happen before the products appear…

Hardware platforms

For netbooks, the Intel Pinetrail platform works and is likely to be the only choice for most of 2011 and until the next generation of netbook platform is introduced. At that point we should expect a lean towards always-on and the addition of hardware video decoding and encoding. The Intel netbook platform should start to look more like the Oaktrail platform proposed for tablets. If we look at the ARM platforms, the dual-core Cortex A9 series of variants is looking interesting for ‘smart’ netbooks and focusing purely on hardware, it’s possible to build a netbook-style device on ARM today. The Toshiba AC100 is one example.

• Timescales for Intel netbook hardware: Now
• Timescales for ARM netbook-style hardware: Now

In terms of tablets, there’s a wide range of choices. Intel are offering Oaktrail which can support Windows for a desktop-like experience and MeeGo or Android for the always-on consumer-style experience. Interestingly Intel also offer Moorestown on which only MeeGo and Android will run to provide a consumer handheld experience right down to almost mobile phone sizes. in the ARM world we have a huge range of choices. We’ve seen MeeGo running on Ti (who work closely with Nokia and are likely to be providing the platform for the Nokia MeeGo products in 2011) and on Freescale, ST Ericsson and other ARM-based platforms. These platforms are targeted at the 4-10 inch segment for highly mobile devices and could potentially be used to make an ARM-based smartbook, just the the Intel Moorestown platform could.

• Timescales for Intel Tablet hardware Q1-Q3 2011
• Timescales for ARM tablet hardware: Now

For the mobile phone space, Medfield is the Intel platform that might appear in late 2011 (more likely 2012) and for ARM, lower-power and phone-oriented platforms are available now.

• Timescales for Intel Handheld hardware: Q2 2011 (Oversize smartphones) 1H 2012 (smartphone)
• Timescales for ARM handheld hardware: Now

Touch

For the phone and tablet market, touch is critical. The experience needs to be fast, multi-touch and up there with the best-in-class. For that, MeeGo 1.1 isn’t enough. MeeGo 1.2 is being built with multi-touch in mind and this is planned for April 2011. Products built on the Beta versions will not be ready for market until at least two months later so unless Nokia is doing their own private work on multi-touch with MeeGo 1.1, high quality products are unlikely before that. With the next MeeGo conference planned for end of May 2011, it is the perfect time to launch a product that will be available in June or July. Whether Nokia chooses to launch their product at this time is difficult to tell. With CDMA support not planned until MeeGo 1.3 a launch in the U.S. would have to be focused around AT&T or T-Mobile but with stronger support in Europe, it would appear likely that a separate Nokia event would happen in Europe for the launch of their products.

• Timescales for single touch products: Now
• Timescales for multi-touch products: Starting June 2011

Battery Life

Intel products will need to be built on Oaktrail or Moorestown for the best possible battery life experience. We are moving to a world where ‘always-on’ will be the standard. ARM-platforms are already capable of offering class-leading battery life.

• Intel Tablet battery life timescales (Oaktrail/Moorestown) 1H 2011
• Intel Netbook battery life timescales: (Oaktrail) 1H 2011 (Cedar View) 2H 2011
• Intel smartphone battery life timescales: (Medfield) 2012
• ARM battery life timescales: Now

Security

Security subsystems need to be in place for carriers and that didn’t happen in MeeGo 1.1. I’m hearing that 1.2 is critical for carriers so it hits the same timescale as those devices relying on the multi-touch user experience.

• Carrier security subsystems in place: April 2011. Products. 2H 2011
• Other products (non carrier): Now

Applications stores

As mentioned, OVI and AppUp are critical. MeeGo will only ship with a basic set of applications and for the best-of-breed consumer devices and to create the developer excitement that is, in-turn, a critical part of the application store, they need to be in place with payment systems.  With OVI expected only on the Nokia devices (Question: What application store will be available for ARM-MeeGo devices that are not from Nokia?) we know that it will be a Q3/Q4 timescale. For AppUp on MeeGo we are seeing some marketing campaigns starting now. Launch is likely to be on the Netbook platform first in order to capitalise on the existing Windows-based AppUp store and to enable MeeGo netbook variants to go out of the door as soon as possible. Remember, netbooks using MeeGo will not need any support for carriers, phone stacks, touch and other elements that can only be delivered with V1.2. Considering that V1.1 is available now and that we’ve already seen proposal OS builds from Linpus, we can assume that existing AppUp partners Acer, Asus, Samsung and Dell will be bringing out MeeGo options likely to drive lower-cost netbooks aimed at entry-level markets initially. Based on that, we should see AppUp for MeeGo netbook UX available in Q1.  For tablet/handheld user interfaces, this might not happen until V1.2 (It’s on that roadmap)

• Application store timescale for Nokia (OVI/ARM): Delivered with first Nokia handheld product after June 2011
• Application store timescale for non-Nokia/ARM: Unknown. Currently no support
• Applications store timescale for Intel / Netbook: Q1 2011
• Applications store timescale for Intel handheld/tablet: 2H 2011 (After MeeGo v1.2)

Applications

Applications are starting to work their way through already. In the MeeGo release itself, media player, email client, calendar, sync, browser and other applications are already being worked on and there are rumors that KOffice will also be offered but as any smartphone user knows, discovery, sharing, enhancement and customisation through 3rd party applications is critical now. There is already a way for developers to make apps for MeeGo on Intel and ARM ‘target’ devices(SDK available here) but there is no support for the Application store yet. Intel have already set up an AppUp/MeeGo portal though.

Preparing applications for OVI is another story. Ovi is accepting Qt applications which will work on some existing platforms and the Nokia MeeGo products when they are launched.

Monetisation (OVI, AppUp) will stimulate the developer ecosystem and this will happen in the timescales shown above.

Finally When Will We See A Competitive Product?

What we see coming out of the MeeGo project is a demonstrator. It’s a complete core with a functional user interface. It’s not what we’re likely to see on end products. In order to make a competitive product; One that has potential to seriously distrupt sales of other devices in the sector requires all of the above milestones to be met. Hardware, Application store, touch, battery life and something we haven’t spoken about yet. The customisation, optimisation and branding process takes months and for a class leading product, could easily take 6 months. Adding in codecs, optimising and branding the content stores, optismising the base applications, checking security, spicing up the interface, writing the drivers and testing is a 6 month to 1 year project. Lets assume that with 1.1, the teams were able to start the process of building a product around MeeGo. In April they will get the features needed to finalise the product and then, along with the integration of an application store, you’ve got another 2-4 months of work ahead. The first competitive products, driven by investment from the core partners, will only hit the market in June 2011 at the earliest. For products from other vendors, expect that timescale to go into Q3 2011 because they will definitely hold back to see what Nokia do, what Apple do, how Android develops, how Chrome OS develops, how the MeeGo application stores grow and even, how Android on Intel develops. The first MeeGo products, in all categories, need to be very special to secure trust from external companies. (Note: It’s likely that Intel and Nokia will invest huge amounts in external companies efforts to get MeeGo-based products to the market.)

Note on In-Vehicle0Entertainment and TV

I haven’t covered these two categories in this article as we’re focusing purely on the mobile/handheld/netbook computing market here.

Summary

We could see MeeGo netbooks with AppUp as early as January with ‘features’ such as quick-boot, lower cost, a simple-to-use operating system with a social-networking slant. We’re unlikely to see too much excitement around these early devices though because platforms and applications need to develop to create products with any major selling points. ARM do have an opportunity to get MeeGo on a netbook-style device in order to create an interesting long-battery-life product.

Tablets could appear in the early part of 2011 as 3rd-parties are already working on UI solutions based on MeeGo 1.1 but for interesting multi-touch products, with an application store, this won’t happen until around June 2011.

The first MeeGo smartphone requires MeeGo V1.2 and won’t happen, either on Intel or ARM until around June 2011. That phone is likely to be a Nokia product and its success will be critical to MeeGo.

Everything up until this Nokia/MeeGo phone can be called Phase-1 led by Intel/Nokia investment. If these products show class-leading features and the developers start to create applications then we’ll start to see Phase 2 products created through independent investment that are true indicators of MeeGo momentum. That story starts in Q3 2011.

Footnote: All timescales are estimates based on current knowledge.

The next MeeGo conference has been announced for San Francisco on May 23rd-25th 2011.

Want a chance to learn more about AppUp? I’m at the Apps World expo in London on the 1st Dec and AppLab in Berlin on the 3rd Dec.

We were lucky enough to get a few days with the Aava / Intel / Meego phone earlier this year and our tests with the handset UX showed that there was a lot of work to do. In a presentation at the MeeGo onference in Dublin today, we saw progress, a good working demo and future planning but still, there’s so much missing. Granted, these user-experiences are just baseline builds to show how the core features can be used but still, it seems to us there are some hooks that need to be added.

With no active icons support (showing number of unread emails for example) and a single homescreen with no widget support it means that product developers will have a lot of work to do to implement these features. On the other hand, the notifications subsystem looks good with support for multiple notification types triggering multiple different notification methods including notification lights, haptics and of course, dialog boxes. We didn’t see any dialog box handling mechanism though so we’re hoping this will be well controlled when it gets implemented.

The demo was done on a Moorestown based Aava Smartphone platform.