Thread: Maemo Missteps, your thoughts?
View Single Post
javispedro's Avatar
javispedro is offline javispedro
2010-06-20 , 22:16
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#319
Originally Posted by Jaffa View Post
There are lots of those sort of apps, I know, but they're not the apps we've been writing.
On the other side, it's the most common kind of app. Yes gentlemen, Nokia is trying to reinvent midlets =) . Qt Mobility = JSR 75 and descendants.

I have to wonder what will happen when we end in a setup where all the system apps directly use underlying APIs, each with its own set of quirks, while all the third party apps are suggested to use the extra abstraction layer in order to keep source compatibility.

Example: native calendar application APIs:
MeeGoTouch -- KCal (possibly?)
MeeGoNetbook -- Evolution
Maemo5 -- calendar-backend

Will Nokia succeed in unifying all of those under a Qt Mobility "Calendar" API? Will it be encompassing enough and at the same time stable and consistent, so that most developers do not feel compelled to use the native APIs to get more features/avoid bugs?
Last edited by javispedro; 2010-06-21 at 00:48.
 

The Following 7 Users Say Thank You to javispedro For This Useful Post: