Hello there.

Some people are keep asking me :
Why you doing this in Flash rather than HTML5. Mobile content suppose to be as small and efficient as possible!!!

Yes, I agree and that's why I am doing it in flash.
And I'll write it here to avoid further questions.

Lets take a google landing page under consideration.
On devices with full web experience you actually reaching the full version of it. And you are not really going to access any particular content yet but just searching for it.

If you using Firefox and have a firebug installed here is the result:


Right, you had to transfer 132kb of data just to access search engine!

Now, Flaemo Landing Page:


Right! 100kb when in fact 13kb has been reused from browser cache even if you cleared this cache before to get there. In practice you transferred 87Kb via network. Basically the way how flaemo is being designed is about efficiency at first place. Bud landing page is nothing exiting really, right?
So lets go further.



And here is something more sophisticated happening. what really happened on landing page. Flaemo read entire graphic user style and just reusing its parts. Going further if you have repeatable stuff on your desktop is going to reuse it from cache. In this case those 9 Google TVs and sticky notes.

Ending with final total 271kb where actually 120k has been retrieved from browser cache! In fact entire engine plus content with all RIA experience is about 150k!. Only 20k more than google landing page. There is even more to come. Partially internal flaemo cache system has been implemented for reusing graphic assets being already loaded. That mostly is for GUI elements. But can be done for widgets as well. It can also be done for requesters.

Let's say 3 buttons sending request for same elements at once. In fact there is nothing to reuse from cache because none of the elements finished loading it. But system can recognize the calls being made and store only references to the requesters. once when desired element is ready just inform them about this fact.

At the end, just for comparison:

facebook.com landing page 113kb what about rest of the content?


twetter.com landing page 305kb what about rest of the content


maemo.org landing page 461kb what about rest of the content


Hey! is not HTML5!

Yes, is not. To be able to represent current flaemo state in HTML5 (not even mention is not fully possible and consistence across the web browsers) I need around 1MB. Do you still thinking HTML5 is the future of the web for mobile devices?

I think for those who going to charge you for that it is.

So please, don't interrupt me at work by asking all this silly questions and let me back to work!

BTW, Flaemo is being build with molehill in mind and if new fully GPU accelerated flash player arrive I'll start to port it. It is being confirmed by flash player engineers this API can be also useful for 2D content and take full advantage of GPU. And this is why I was trolling about lack of flash 10+ support on N900. it will be huge disadvantage to don't have new flash player on your device whether you like it or not. It will be actually bigger than lack of HTML5 support.