Everything and the Mobile Software Universe…

Let’s find out why this shift means a lot for Rich desktop and Mobile Applications

Google web APIs are simply the most used and prevalent today, allowing a full range of mash-ups and new web services…but what not a lot of people know is that it was simply not legal to use Google maps APIs outside of a web site, so namely in an application!

This is why only Google were providing native applications around their maps services for mobile phone (iPhone apps, WinMob, J2me), and PC (Google Earth)

And now they changed their mind:

There were both technical and legal challenges blocking AIR support in our API. AIR has a different security model, which required a number of changes to the “internal plumbing” of the API in order to implement our delayed-loading model, where the actual implementation of the map’s functionality loads dynamically from Google’s servers once the application launches. Also, our Terms of Service used to specify that the Maps API could only be used for online web applications.

Now that both the API and Terms of Service have undergone a facelift, we are releasing the first version of the API that will allow Flash/Flex developers to bring Google Maps to the AIR runtime.

Google developer blog

This is is a big acknowledgment from Google of the relevance of desktop and mobile rich applications to access “in the cloud” data, the browser is no more the only deployment method for web services, and the nice work done by Adobe around AIR/OpenScreen is pushing this idea making it more and more mainstream…iPhone apps for the most part are specialized access to web resources, and what to say about Android? This trend is also followed by Nokia through its Trolltech acquisition for the QT technology, check my little post about this one here.

So thanks Google! let now see what’s coming from the web…and this old boy called desktop and its mobile children!

For those that are following this blog…you’ve seen that I’m talking frequently (hum not as my posting recently ) about low cost phones. It’s just because I mean it, we know how hard it is to complete a phone software on very cheap platforms. But here we are! A phone is out, and it’s a Sony-Ericsson one, well yes we are proud checkout the press release (it is just all over the web today):

Open-Plug Powers the New J132 Mobile Phone From Sony Ericsson
Monday November 24, 3:00 am ET

- The Open-Plug Software Suite for Mobile Phones Will be Rolled out in Large Numbers Across Europe and Asia

SOPHIA ANTIPOLIS, France and LUND, Sweden, November 24 /PRNewswire/ — Open-Plug, the specialist in software development environments for mass-market mobile phones, announces today that its ELIPS application suite is embedded in Sony Ericsson’s J132 mobile phone. The J132 is a talk and text phone with FM radio and stereo hands free kit.

"We are very proud to be cooperating with Sony Ericsson, one of the top leaders in the mobile phone industry", said Eric Baissus, CEO of Open-Plug. "This is an additional demonstration of the maturity and performance of our ELIPS solution."

Open-Plug has developed the ELIPS software suite to address the strategic market of low cost and mass-market phones. The demand is exploding and drives very significant volume worldwide. Thanks to the performance and flexibility of its underlying award-winning component technology, ELIPS enables fast development of new mobile phone models and simplifies implementation of new software features and user interfaces.

Open-Plug’s solution is a major step forward towards the reduction of development time and costs for handsets and mobile applications. ELIPS is attracting more and more software developers and handset makers who want to re-use their investment from one platform to another and develop variants in record time. It is the result of 5 years of R&D and includes several patented technologies.

About Open-Plug

Open-Plug creates and commercializes ELIPS, the first open application development environment designed for mass-market mobile phones. Already shipped in millions of devices, ELIPS enables software companies, handset makers and operators to create and deploy mobile applications, rich user interfaces as well as complete software solution, in record time.

Founded in 2002, Open-Plug is a private company financed by leading international venture capital investors. Headquartered in France, the company also operates in Taipei, Taiwan R.O.C. Open-Plug is a member of the LiMo Foundation (Linux Mobile Foundation).

For more information, visit http://www.open-plug.com

…well technically this is the contrary , check it out at Linux Devices

In kicking off the conference, Nyström emphasized Nokia’s interest in horizontally broadening Qt support across as many platforms as possible. Asked whether the company would also target new verticals, such as automotive infotainment, Nyström did not rule out the possibility. However, in a private interview with LinuxDevices, he admitted, “For Nokia, the real value of Trolltech is in Qt.”

Qt Software Chief Sebastian Nyström

Ok, everything is said: Nokia acknowledges that they have bought Trolltech for Qt as a multi-platform runtime to deploy services, on desktop and devices…I’m really curious to see in  what Nokia morphs…again.

Thanks David for finding this nice one:

found here.

…looking at the prices, and compared to the BOM of an Ultra low cost phone (now around 15$ for the best OEMs)…well you understand why smartphones are not cheap…and how difficult it is to do an Ultra Low Cost phone!

…I just can"’t imagine the margins chip manufacturer are doing on those application processors.

This really back-up what I’ve exposed here about application processors.

Any comments?

Thomas.

The Linux community has come up with a bunch of new technologies to bring the UI eye candy on Linux to the next level…following the path of a well established player : Apple with its 8 years old compositing window manager Quartz.

But as it may happen way too often in the Linux desktop community the emphasis is on the technical aspects , not at all  on the ease of use and usability improvements: check the following nice/fancy/eye blowing demos, and after the wow effect … think about what it brings.

Here is an interesting Beryl vs Vista videos: the focus is on effects only, except form the clear Apple borrowing (dock, window in/out effects) the Beryl side is just as unusable as the Vista one can be…but you have eye candy , and a wiz/bang  teenager environment (jackytouch for the frenchies )

Another one with Compiz-Fusion, same conclusion:

…just try to find a utility, a user experience meaning to this fireworks….well nothing, in the same vain as vista windows effects and switcher you deactivate to speed up your PC. Ok the 3D cube is lovely, but come on, playing a 3D game just to switch between workspaces can be called a waste of time, I want to be efficient to do the things I really care on my PC, which ARE NOT looking at the animation between windows!

Then come this little refreshing Linux gem, and, I want to say of course, it is not coming from the "raw" desktop engineering Linux community, but from a lab (ok, a french one ), Inria. It is called Metisse  : and at last it clearly states "Usability study and experiment before nice effects!"

Metisse [1, 2, 3] is an X-based window system designed with two goals in mind. First, it should make it easy for HCI researchers to design and implement innovative window management techniques Second, it should conform to existing standards and be robust and efficient enough to be used on a daily basis, making it a suitable platform for the evaluation of the proposed techniques.

Metisse is not focused on a particular kind of interaction (e.g. 3D) and should not be seen as a new desktop proposal. It is rather a tool for creating new types of desktop environments.

Quote from the Metisse  web site.

Checkout this simple idea about copy/paste: why on earth it is not like that today….

This one shows also some interesting usability concepts:

[SonyEricsson is promoting a new Application Environment mixing Java ME and Adobe Flash Lite: Capuchin. Blogger Thomas Menguy tries to describe it and evaluate what "yet a new" development platform means to the industry ].

Sony Ericsson had a nice webinar last Thursday, interesting held through Adobe E-Seminar:

“Flash Lite meets Java ME on Sony Ericsson phones with Project Capuchin”.

At least now we have some information about Capuchin, and I’ll sum it up for our beloved busy executives:

• A technology that allows developers to make the UI using Flash Lite and code the business logic and access to the platform services with Java (ME).
• A development environment with PC based tools (Adobe CS plugin for flash and Eclipse plugin for Java), simulators and a specific runtime embedded in SEMC phones.
• The deployment is done using the well in place Java deployment environment (jar are used, same signature, etc).

Here is first a transcript of the capuchin webcast, then as a conclusion I’ll throw out my thoughts about this and its impact on the industry (if you are still there…).

Project Capuchin Web Cast transcript

Capuchin is about mixing those two worlds, and enforce UI designers and developers relationship.

Why the Capuchin name : it is a monkey like tamarin…the name of the Adobe Action Script VM.

Here is a high level architecture presentation of Capuchin:

Flash content is embedded into a .jar and can be launched by some Java code, then, thanks to the Capuchin API the Flash Action Script can access the various JSR or any other Java class of the project.

Here is below how an accelerometer API may be available in the Flash Action Script of a Capuchin Application:

The Capuchin API works both way: flash to java and java to flash.

What Capuchin is bringing:

Flash development:

• Extend current limited APIs with the use of JSR
• Secure Flash application
• Deploy flash as java games, distribute Flash content through existing java distribution infrastructures

Java Development

• Clear separation between business code and UI
• Nice development tools
• Professional UI tools

How to use Capuchin:

3 main ways to do:

1. Packaging pure Flash Lite content using jar
2. Java Midlet using Flash Lite for the UI layer
3. Java Midlet using Flash Lite for PARTS OF THE UI

Adobe has a nice technology: mxp, format for packaging extensions. Capuchin use mxp to package the APIs that will be mapped into the Action Script.

There is an Eclipse Capuchin Plugin to create those APIs declaration (see above) as they will be usable in the Action Script written in CS3. This tool outputs an XML file which will be used to output Java Classes for the java part to be implemented …. and Action Script classes to be used in CS3.

Everything is then packaged in a .mxp installation package. SEMC will provide some mxp already (Bluetooth , others…)

Demo time:

The webcast then featured a demo:

swf2jar :

Goal here was to show the tool to convert a swf to a jar, swf2jar: very useful for packaging because a flash game today…end up in the image folder when deployed in a SEMC phone ….

Calendar component:

Project Capuchin plugin for CS3, with mxp packages. The intent here was to show how to use Java services in a Flash Lite content

There are some “Platform components” in the library:  in the AS editor, it is possible to import for example the package com.sonyericsson.capuchin.calendar.Calendar

… to import the Platform classes,  so it is now possible to use the Calendar class as a normal Action Script, even if it is a Java Service.

One word about the toolchain future:

In gray: Not done today:

• Flash Emulator will be connected to Eclipse to use java services directly and not only stubs
• UI library: a flash widget library will be developed
• Connect everything to the existing SEMC phone emulator
• Work with adobe so that in device central, when a SEMC phone is selected the list of available mxp would be provided.

What will be published soon:

• First phone : C905, compatible with capuchin APIs
• Capuchin APIs,Java Classes
• swf2jar tool
• Capuchin API generator , eclipse plugin
• mxp packages with source code
• capuchin test and video tutorials
• demos applications

=>check here http://developer.sonyericsson.com

(final: October)

SEMC Capuchin will be present at Adobe MAX in San Francisco and in Italy in December!

Some Q&A with no major questions…mine were not answered:

• What is the implication of Adobe in this project?
• What is the implication of Esmertec in this project?
• Is there a roadmap to have Capuchin on other platform than SEMC ones?

Some points about this initiative:

• SEMC has already done a large part of their applications in their feature phones in Java, and they have a strong Java commitment with Esmertec, so on SEMC phones Java is the preferred development method internally….and now with Capuchin, externally as nearly all the platform services are already available in Java.
• With the point above, and knowing that some part of the SEMC feature phones themes are already in Flash, merging Flash Lite and Java was a natural choice for SEMC

• Flash Lite choice is the only one possible for today mobile phones (CPU/Memory)…but is really not a complete and efficient UI application frameworks, it lacks …widgets! So SEMC plan to develop some new ones, hum wait, Adobe Flex is not about that? Bringing application development to Flash?

• Not sure about the porting of such a technology on other platforms than SEMC … but from my knowledge only another one has made the Java choice: Google Android where all the platform services can be accessed through Java, but I don’t see any incentive for SEMC to port it to Android

Conclusion

So we have a new Application Environment, with its own SDK, that will certainly be only available on SEMC platforms….Capuchin one will complete this never ending list:

Are we still talking about cross platform development? About consolidation and standardization?  NO

The industry is pushing the other way, and really this is NOT AN ISSUE.

Services and applications developers have learnt how to reuse code across platforms, how to architect their code and services so that it is easy to change only the presentation and the adaptation to the platform: after all developing a UI for a 800*480 screen and a 176*220 is just something completely different, and really not a big deal if your UI is uncorrelated from your services; Capuchin helps that, as many other technologies.

All those new Application Environments are bringing to Mobile Platforms  great core value for services deployment :

• openness
• great tools, ease of development
• focus on user experience and UI
• deployment/packaging/distribution strategies
• security

And we don’t want a “one size fits all” environment, it is simply not true in an industry where the forms factors, capabilities and designs are so vastly different. Differentiation is key in this market, just open the platforms with nice and open development technologies, it is enough!

One big trend we can foresee also is that the platform vendors have no more software complex, and when you look at the list above, nearly all the initiative are coming from OEM, and not really from pure software companies (notable exceptions: Android and WinMob)….PC based paradigm seems soooo far away!

6 months of 3D in flash in 10 minutes from Galdric on Vimeo

Found here: http://www.hebiflux.com/blog/2008/06/12/video-6-mois-de-3d-en-flash/

Seen from the great usability/UE/User experience maintained by TAT:TAT » The Astonishing UI-blog

A Tactile feedback … made of fresh air! (Ok, ultrasound)

Stunning….

[Intel is moving fast toward MID: Mobile Internet Devices, and just bought an open-source mobile centric company: OpenedHand… blogger Thomas Menguy tries to look at the Intel current strategy to get some shares in the mobile market].

For years Intel has repeatedly failed to get a piece of the Mobile phone 1 billion devices a year cake.  The latest known attempts was the infamous XScale processor, too big, too slow (albeit a high MHz count) for the smartphone application processor market, it has been trounced by the usual suspects ARM based manufacturers (TI, Samsung, …).

Intel is coming back to its roots: x86. And their weapon is the ATOM processor. AT first it was designed to be a very power and simple x86 core to be used in multi core processors (with a lot of core) … but it’s strength was fully applicable to a nascent market: the UMPC. And from an UMPC to MID ( like the Nokia 770/800/810 Tablets)  there’s not a lot of differences.

Anyway ATOM is not competing against archrival AMD, but …. with ARM manufacturers (Nokia Tablet, ipod Touch are ARM based), with a big edge: not so because of the performance (even if it is faster), but it can run windows! It’s a full x86 chip. Ok, power consumption is still faaaaar from an ARM based system, but the Moorestown  will lower this barrier:

Intel has publicly committed that Moorestown will have at least 10 times less idle power consumption than the previous-generation Menlow platform.

http://softwarewiki.intel.com/mid/Moorestown

….Even if running windows may help convince some manufacturers and users, there is currently a trend for “exotic” software platforms that are well, simply doing their job. A MID is NOT a generic PC: Nokia Tablet OS, MacOS X mobile ( ipod Touch/iPhone), Linux based UMPCs, Samsung latest smartphones…upcoming Android and Limo…are all “windows” decomplexed interesting platforms.

Intel decided to become more than a silicon vendor: they want to go the system provider route, and for that, of course, they need their very own software platform (yes a new one…):

 

The video above is simply a mock up of what it would look like….

This software platform is called Moblin.

Moblin 1.0 is (was) a sister project of Nokia Maemo (foundation of Nokia Tablet OS): same Application Framework (Hildon), nearly the same API’s, same UI framework. To be honest, and according to Intel own words:

Moblin has “failed to generate much interest” among developers. “Moblin 1.0 wasn’t successful in creating this community push,” Hohndel (Intel’s Dirk Hohndel, director of Linux and open-source strategy,) was quoted as saying. “Having a vibrant community push is the winning factor.”

Linux Devices – Moblin switching from Ubuntu to Fedora

But Intel needs a differenciator: Intel and its OEM will now compete with Nokia, Android, Apple….Intel needs fancy stuffs, so here is :

Moblin 2.0: still Linux based for the lower layers, but with a new graphical interface based on: Clutter and Compiz: Clutter is a “modern” (ok still some glib ugliness in it)  2.5D widget framework, and compiz a very nice 3D window manager, both based on OpenGL (ES).

Here is an example of a Moblin Clutter application:

 

 

Around this Intel is planning a lot of services and Applications, like the Contact Epicenter, or a Mozilla based browser, Fennec (incidentally same choice as Nokia fir its tablets…all the other platforms being webkit based).

So now we have this announcement: Intel acquires OpenedHand.

And when you look at OpenedHand projects:

• Clutter : You know it now
• gUPnP : UPnP library
• Matchbox : Window Manager + application used….in Nokia Tablet, OLPC and OpenMoko!
• Pimlico : set of Mobile PIM Applications
• Poky : An open source software development environment for the creation of Linux devices….

So basically OpenedHand brings to Intel some key pieces for its platform, especially Clutter ….and the tools ALL the Linux vendor are missing: a Platform Builder to help OEM to put their platform in place! (Only Microsoft has it with the Windows Platform Builder, to adapt WinCE winMob to various hardware platform, to get the needed modules, etc.).

But perhaps the key OpenedHand assets for Intel, are the people behind OpenedHand, Kudos to them to be their since 2000, and now at Intel!

Intel is serious about this platform, beware Symbian, Limo, WinCE, MacOSX mobile and Android, here is a new credible platform to look at!….Anyway Intel is  first a silicon fab, down to its DNA, so the open points will be:

• Is Intel  able to commit long time efforts to software?
• Software support to its OEM?
• And the biggest one: Is Intel able to design a software platform with a great user experience? .

The last point is crucial,WinMob and Symbian has failed in this regard, even if they are done by software companies.

Putting Open source technologies together is really not enough to make a consumer product, I’m eager to see if Intel has, or is hiring some usability and design experts (and not only software engineers).

Anyway having a new credible, deep pocket actor in the industry is always a good news…and from MID to smartphone, the gap is really blurring, we may expect some great devices!

Really great pragmatic article

This article covers aspects of ActionScript 3 that would be helpful to C/C++ application engineers transitioning to application development in Flex and Flash.

Read on more here., and the following one  here (same blog)