HP not likely to support Qt in webOS development, probably not going to support Android, J2ME, or Visual Basic either | webOS Nation

HP not likely to support Qt in webOS development, probably not going to support Android, J2ME, or Visual Basic either 17

by Derek Kessler Sat, 02 Apr 2011 7:55 pm EDT

Ari Jaaksi left Nokia to take charge of HP’s webOS development, and there’s been a low rumble of speculation that his MeeGo-soaked Nokia roots might result in support for Qt. If you might recall, Qt was the open source programming language of choice for Nokia’s Maemo mobile operating system, and continued to be after it’s merger with Intel’s Moblin into the MeeGo of today (which Nokia has since practically dropped in favor of Windows Phone 7). So would Jaaksi’s hiring by HP signal an intent to adopt Qt?

No, if Jaaksi’s comments on his personal blog are to mean anything: “Some people commented to my last post and suggested that we'd take qt as a part of our tool set. I don't see that happening. WebOS is much easier.” He goes on to discuss how awesome Ares and PDK development are, extolling the virtues of familiar web technology tools. Jaaksi also says “Other tools would just make things more confusing and provide no real added value.” Subtle, if unintentional, dig at the support-everything-under-the-sun-please-make-apps-for-our-platform BlackBerry PlayBook? Maybe. Frankly, we’re glad to see HP sticking to their guns with webOS development. Ares web tech apps and PDK native development make a powerful combination where lightweight apps can be easily built with Ares and heavy stuff with the PDK, and soon enough you’ll be able to combine the two in hybrid apps to cover the middle ground. There’s no place in that spectrum for a standard like Qt, even if it has been known to run on webOS.


I'm not sold RIM's android endeavors.the playbook doesn't actually run android apps, it's sdk just shares a lot android api's.this means there will be some work involved in getting android apps into blackberry world. Also as the android continues to evolve it will create further fragmentation.

I didn't think android fragmentation was really an issue until I started reading comments in the marketplace about how some apps don't work well on some devices. The playbook method of compatability certainly won't help.

This strategy my work for RIM because the their tablet doesn't really have any differentiatng features from the competition. My thing is, I don't want android apps on my webOS device if they don't behave like webOs apps. That means support for just type, stacks, and quick actions. I'd much rather see HP compel devs to make true webOS versions of their apps than get a flood of half-featured apps that won't stand the test of time.

Of course they shouldn't support it officially. At least not as long as they haven't finished their own PDK and SDK and the hybrid Apps (webOS 2.x... 3.x etc...). This all has to be worked out in a good manner and provided with a very good documentation to attract developers.

Later on they can help to empower other frameworks as Adobe AIR, QT and whatever else there is under the sun.

If somebody wants, he can already use QT for Homebrew in the meantime.

I agree with his sentiments about dev confusion. One of Nokia's big problems is they supported an absolutely ridiculous amount of languages and platforms. You could use Qt, WRT, Java, plus possibly several others, not to mention there was s60 3rd edition, s60 5th edition, s40, Maemo/meego. It just became a mess from a getting started standpoint.

I wish Palm would have dropped the PDK and went with a webGL method for Enyo since I think it would make the development style more cohesive, but I understand the huge wrench it would have thrown in existing developers ability to port things. Games like Need for Speed are not going to get ported to webGL unless Palm had a huge marketshare, so I realize they weren't in a position to push a standard.

Nokia was been telling developers to focouse on Qt for years now fir Symbian and MeeGo and soon S40(feature phone platform)
The point of sporting different languages is if you know Howe to develop using say java then use java don't worry about the other stuff of you are a bew developer start with Qt .Nokai had a problem convincing people to develop apps fir them even thought they had the most marketshare for smartphones they just did not have a flag ship phone that soled engh because they were never on any US carrier.

Of course by supporting multiple languages you CAN catch more developers. This is the same old question of quality and quantity... You should only do so much, that you can guarantee a high level of quality (APIs, Documentation, Development Tools etc...).

If your company is capable to provide this for 20 programming languages... then keep it going, but most probably not... Even Apple and Microsoft aren't able to do this.

In earlier times the companies just threw out their software and enabled the developers to program it. That was it. And every developer watched his feet and tried to develop as good as he could.

With the iPhone nevertheless those developers got used to be treated much "better" (and with less freedom of course) by getting the whole Tools and Documentation in a good quality. And now we are in a world where there are a lot of systems that compete and where the fight for developers is crucial for each company. That's why HP at this point can't support all those other languages officially...

RIM does it, but if you look closer to it, they actually only support their native one "really" (with official tools etc.) and even there it's not really compelling. Their approach is closer to that which got obsolete already.

Emily Litella: What's all this talk about not supporting Quick Time? That's just crazy!

Chevy Chase: Um, tht's Qt, not QuickTime.

Emily: Oh, nevermind.

I'm with Emily. i thought they were talking about Quicktime. Honestly, i wonder how important it is to sales if the user can't tell the difference and doesn't know what you're talking about.

i'm sure this is developer stuff and maybe it's important to them. Weird though.

The problem with supporting somebody else's ecosystem is that peeps wont developer for yours. RIM having android is just saying. Don't develop for RIM, develop for android.

I've been developing for WebOS since day one and also have experience developing for other mobile platforms. I can honestly say developing for WebOS is night and day over other platforms. There is really no "need" to support other frameworks when HP/Palms own mojo & enyo are light years ahead (as far as simplicity goes). Any developer worth his salt would certainly find developing for WebOS a nice welcome. I'd prefer it over something like VB or Qt any day.

You are right, but I know some guys who have worked for 10 years with language X and DON'T want to switch... For them this would be appealing to support their language too. Nevertheless HP shouldn't do it. Better loose some developers because of this than loosing a lot of good ones because of a bad execution of your SDK/PDK Tools.

But you are right, developing for webOS is the most simple task compared to other platforms :)

Minor correction - Qt is library/toolkit for C++ not a programming language on its own.

Nokia did not drop MeeGo for WP , MeeGo was demoted to what ever ditructive services is there is still a MeeGo Nokia devices persumaly a phone comming out.
QT is a powerful developing tool thoe to bad it is also get down sized unless MeeGo takes off in a big way.

Yes, they are going to keep Meego as a little research-project. Nothing serious unfortunately.

To me this was the second most appealing platform after webOS.

He's done wonders for Nokia. Glad to have him on board. I'm sure he will bring the same level of success that Symbian is experiencing now.

He wasn't responsible for Symbian, but for Meego. Which, to be hones, was a really good OS. Just that Nokia never gave him any push... It was even worse than anything that Palm or Sprint ever did to webOS.

If Nokia would have given Meego some more decent phones and gave him a push, it would have been a hard time for me to choose a phone. Luckily Nokia stuck to their $%!&/?§-Symbian platform so that it was easy for me to choose.

You know what's funny? Qt is already supported in webOS 2+ since Luna (the launcher) uses it as it's rendering core. And that's maybe the reason Pre 2 is so fast compared to the older devices.

seriously. Why not give everyone access to Qt?

And why can't PDK apps use Qt libraries? (Obviously they could bundle it themselves, but why?)
We could pull all those developers away from Meego REAL quick by supporting Qt. We'd have the easy ones right away (Opera, Fennec (Firefox Mobile), and others) and we could grab the others on the way.