[QUOTE=attila77;780916]People will not develop for MeeGo - they will develop for Qt. ...

I have seen this argument several times, but I still don't get it technically. If you write for Qt for the desktop, you may e.g. make clever use of the third mouse button. You may make interesting applications based on hovering. You may save and load your data in application specific places. You can popup lots of sub windows (e.g. like gimp does). You can make heavy use of read/write cycles to the hard disk. And I'm sure lots of other decisions that work just fine on the desktop, but don't scale to a mobile device with its different constraints. How does Qt take care of that? E.g. an Android application is supposed to automatically store its entire state on close. How does Qt/MeeGo do that, or doesn't it? Is it up to the application programmer to decide whether he wants to store the state, or popup a window asking whether to save the data?