In theory it is great, but I'm waiting to see if they deliver.
If Symbian 4 / MeeGo suck for end-users, it doesn't matter how good the SDK is.<p>On the other hand Nokia is dominating the low-end phone market by an order of magnitude. And personally I haven't bought an Android phone already because they are so damn expensive and I don't want 2-year contracts. And in Europe a lot of people are holding off from expensive phones just as I'm doing, preferring to go cheap with 1-year contracts or with PrePay options.<p>So it's not like they don't have what it takes to be winners.
We're currently evaluating a Nokia N8 for a contract. I know that the article is about the next step for Nokia, but the fact that they are releasing this phone tells me that Nokia is not winning.<p>The phone is barely usable.
QT Quick (Nokia), Clutter (Intel) and Core Animation (Apple). Would it be fair to say these are modern toolkits with similar goals? Does anyone in the know have an opinion on which one's doing it the most right?
I don't care much about Symbian or MeGoo, nor do I for KDE. Qt is wonderful though. I can develop applications on my Linux machine and just compile them on Windows without having to have to run it. Also, it's quite mature with a good feature set, reasonably fast, reasonably integrated in various platforms and has an adequate SDK (though I don't use that). The doc's are quite good too.
Hmmm no. Nokia has definitely not won. One of the big problems with cross platform toolkits in general is that the platforms are ... different! They have different capabilities and completely different user interface paradigms. A good Android interface is not a good iPhone interface and these days people are coming to expect a polish that you will just not achieve with cross platform tools. The only cross platform technology that ever really succeeded is the web.<p>That they have abandoned MeeGo was probably a good idea, but in my opinion it just shows how desperately they need something new and good. They don't even have what Microsoft now has and I doubt they will be able to regain any significant market share after Google, Apple and Microsoft have split the mobile market between themselves by the time Nokia finally releases something that doesn't suck.<p>Nokia is in big trouble and I really don't understand how people can not see this.
I don't understand, as the article suggest, why it will be good for Nokia if Qt will be ported to Android, iOS or WP7...(?)<p>Here in Europe, Nokia is still #1 in dumbphones area, and what I see is that there is still a large number of people who doesn't need/want smartphone. So Nokia will probably stay strong in this still-big area. (But they undoubtedly will have a problem in the smartphone segment.)
The promise of "write once, run anywhere". Where have I heard that before?<p>Somehow I doubt Nokia would be particularly motivated to maintain any Android/iOS/WebOS versions of Qt - assuming they bother to write them at all.
Seems like there are lot of "if's" and requirements that things go according to plan.<p>Also... C++? I'm not that enthusiastic, really. I'm not a Java fan, but all in all, I think I'd prefer it at this point, if for nothing else than being a bit simpler and getting GC built in.
Saying "by next year" and "may have already won the developers battle" in the same paragraph really flags this as wishful marketing.<p>Plus there is a lot more to wooing developers than just toolkits. But Qt is still something I enjoy using.
"We have no money to support developers so we are going to make you all use one toolkit"<p>Yes, we all know that what we need is <i>another</i> platform to target. Get a clue Nokia. Its all about apps now, and this is the priority for app developers:<p>* iOS<p>* Android<p>* WP7<p>* The fluff in my navel<p>* Nokia Qt<p>Pretend all you want, but this is the order my clients budget for.