Tell us what you think – Take the Qt SDK survey, earn points and win a device

Published Friday May 27th, 2011 | by

We powered up our vintage ‘download-o-matic’ mathematical robot this morning and made it crunch some numbers on how many people have downloaded our new SDK.

After several minutes of mechanical chugging and robot sounds it produced a dot matrix printout showing how many people have downloaded the Qt SDK 1.1 since it launched a few weeks ago.

The results (and the robot is never wrong about these things) were pleasing. A large number of people, even larger than we expected, have downloaded the SDK. We also know from talking to developers that lots these downloaders are actively using it.

Now that we know lots of you out there are using the new SDK, we want to hear your thoughts about it. Our motive is simple – if we know more about what you like, what you don’t like, and what you want, it increases our chances of making subsequent releases even better.

We actually don’t even mind if you haven’t used the new SDK yet. If you are using or have used any Qt SDK we are interested in hearing from you.

It’s a straightforward survey that will be available for a few weeks. We are so interested in hearing your opinions that we will give every survey respondent 250 Qt Developer Network points for their account.

Even better than this, we will be giving five lucky developers who respond to the survey a Nokia Qt developer device – and it is NOT an N900 or a Symbian device (note that we are not setting a date for this – we must wait for the device to be announced :) ).

So…you have some good reasons to tell us about your experience with the Qt SDK. We’d love to hear what you think and what you want added, removed, changed and improved. If you haven’t used the new SDK yet, why not download it now and fill out the survey once you’ve tried it out.

UPDATE: The survey has now been closed.

Did you like this? Share it:
Bookmark and Share

Posted in Community | Tags: , , ,

25 comments to Tell us what you think – Take the Qt SDK survey, earn points and win a device

Mazur says:

Already send to you :) .

Alan says:

Done, but gosh, the survey is primarily focused on mobile development. I might go in that direction some day, but right now my needs are for desktop development.

When can we hear those numbers? Or are they a secret? :)
I was downloading the SDK while it was in beta, but then I changed to it’s components from my arch repository. I’ll probably download the complete SDK when my project is in more or less complete and want to test it in the simulator. Unfortunately didn’t found the simulator integrated in Qt Creator from the repo. :(

夏苗仁 says:

the speed of network is slow .How can we download Qt SDK in a short time?

faenil says:

I have completed the survey…but no 250points in my account and the email is right :)

is that normal?

I’m writing it here just in case other people are wondering the same ;)

And who knows, I could be the lucky one to win the device :D

SABROG says:

It is a fourth survey for me from Qt for five years, fourth try to win a device. :)

Henry Haverinen says:

@faenil: we’ll give you the points with a script that we’ll run when the survey closes, so please be patient :-)

@MladenMilankovic: I haven’t thought about that yet – but if there are any findings that would be useful for everyone contributing to Qt, why not!

@Alan: thanks for responding, it’s important for us to get feedback from non-mobile developers too.

Qter says:

I wonder why the SDK is so large(1.5GB) for windows. Can you make it smaller?
btw, I think you’d better take more advertisements or promotions in universities and schools.

jiaer says:

I want Qt/3D is a part of QTSDK.
and completer will not display when the STL iterator be called in QtSDK. But It’s ok in Qt 4.7.0 etc.Can you fix the Bug?

Javi Moya says:

I hope that people that are always crying about QML stuff take this survey and express their thoughts. This is the place where we can change things. Maybe Nokia hear us.

My opinion is clear:
if Qt/QML is not going to officially target the 2 main mobile ecosystems (iphone and android)… I have (and most people) no interest in learning it.
And in desktop… I don’t see me using it.

serkol says:

I totally agree with Javi Moya.

I have ignored this survey because it is focused on mobility and QML, but Qt mobility does not interest me, because it targets only the officially dead Symbian and the dead-in-the water MeeGo. So if Qt mobility has no future, I don’t quite understand why QML has number 1 priority or why it is needed at all…

But I have filled the survey, so that my voice is counted.

Henry Haverinen says:

@Qter: Thanks – one way to help with the install package size is to use the online installer and unselect all the components that you don’t need.

@jiaer: could you please file a bug report about the STL issue at The 3D research project is going on and I agree it’ll be a great addition to Qt and the SDK once it’s ready.

@JaviMoya, @serkol: thanks for giving feedback from your point of view.

I think it is important to keep Qt as a single toolkit for all its platforms; desktop, mobile and embedded, instead of becoming a collection of related toolkits. We don’t see Qt Quick as a mobile specific technology, but as Qt’s solution to creating more dynamic user interfaces. I believe easier ways to create animated layouts, smooth transitions between UI states, and graphical effects that communicate context information and give intuitive feedback to the user would improve user experience on desktop platforms, too. That said, the technology is not ready yet, for instance desktop components are in the research phase right now, so Qt C++ will be the right choice for (most) desktop user interfaces for some time. I agree we also need to cater for the huge legacy of Qt C++ applications, keep the existing customer code running. There will be room for both C++ and QML.

Qt mobility is a separate project. Even though it’s perfectly fine to have modules in Qt that are mainly useful on some platforms only, the name of the mobility project doesn’t do justice to its platform support. In Qt 5, we’d like to remove the difference between “Qt proper” and “Qt mobility”. Some APIs, for example system information, maps, multimedia, service framework, are already cross-platform and useful on many platforms, some will remain useful for some platforms only. Similarly, we can continue to have have modules like ActiveQt that are useful on desktop platforms only.

JubiluM says:

@Henry Haverinen:

You’d probably be surprised to know how many non-mobile developers Qt has. I’d even claim that you have more desktop programmers than mobile. Maybe you/Nokia should make a research of how wide Qt’s usage is so you’d get a picture?

There are many desktop projects and developers out there who necessarily read or comment blogs etc. and it would be valuable hear those voices also. This survey really doesn’t give you valuable information other than concerning mobile/quick. But anyways, I will also fill it.

Thanks :)

Samer Kour says:

Thanks to nokia regarding this really good SDK . I hope to be along with nokia in this prefect project at the end . go ahead .

Engineer Samer Kour. Syria

Henry Haverinen says:

@JubiluM: We do know that Qt has a huge number of users targeting desktop platforms and embedded non-mobile devices. We’re talking to developers who use Qt for education, scientific research, commercial applications, open source projects, embedded user interfaces etc.

It is true that we made this survey to get feedback on the new features of Qt SDK 1.1, which are very useful on mobile platforms. Qt SDK 1.1 is a major milestone in mobile Qt development. But we are also very interested on the feedback from the users who are targeting non-mobile platforms.

W. Dobbe says:

Henry, thanks for your comments.

However to call the Qt C++ applications (that probably make up for 99% of all Qt applications) “legacy” is a wrong point of view in my opinion.

serkol says:

@W. Dobbe: Right to the point.

“Legacy” is something that is a burden and everyone wants to get rid of.

It’s funny that Qt team looks this way at 99% of their user base. Well, get rid of this “legacy”, and you will be left with 1%, and very soon with 0%. And you will not get any new user base, because nobody wants to waste his effort developing for Symbian and MeeGo.

I hope that you will change your view regarding your “legacy”.

unregistered says:

I would say that “I agree we also need to cater for the huge legacy of Qt C++ applications” is way different (better) than “I agree we also need to cater for the huge amount of legacy Qt C++ applications”.

I don’t think he sees them as a burden. But maybe that’s just me.

Henry Haverinen says:

@unregistered: Thanks :-) I definitely see that the existing Qt users and new Qt users, who choose to create applications with C++, are bringing huge value to the Qt community.

loladiro says:

I have to agree with the commentators before me.
I don’t do mobile development and I have never used QML.

Guido Seifert says:

I cannot even answer the first question. I usually don’t use the SDK at all. It just feels ‘yucky’ for me. I always have the feeling, that it wants to impose the workflow the developers deem appropriate on me. The way I have to use the mouse or keyboard, how I arrange the widgets, does not feel right for me. Sorry, I really love Qt and seem to be one of the few who are eagerly waiting for Qt 5.0 even though I expect a somewhat bumpy transition. So it certainly isn’t some automatic rejection of everything new. I tried the SDK more than once, but always returned to kdevelop. When I develop for mobiles I often do all the development as far as it goes with kdevelop and only in the last steps, when interaction with real hardware is necessary, the SDK is used.

Steven Starr says:

I am a Linux Software Developer, for those who haven’t given QML a try you real should it’s actually quite awesome. I original had my doubts about QML and Wayland but after giving them a try I realized those to technologies are going to revolutionize software development for opensource platforms.

FangPeng says:

Is basemap can embed in pyqt4?How can do it?Thanks!

Eddy says:

I recently started looking int QML and it’s really great!

BTW : are those numbers known at this moment yet? It has been almost a month since the survey started.

Henry Haverinen says:

It’s time to wrap up the survey! I’ve now contacted 5 lucky developers, who will receive a Nokia N950 device – congratulations to the winners! Next, we’ll add the Qt developer network points to those of you who left your Qt Developer Network email address.

We got A LOT of feedback – thank you very much! I haven’t yet finished analyzing the data or reading all the comments. There were around 1200 submissions, from users targeting at all the operating systems of the SDK. I’m surprised to see how positive the feedback is in general. Now, I’ll go back to analyzing the numbers and reading your feedback.


Commenting closed.