Harald Kjølberg

Qt Customer Survey 2018

Published Monday January 14th, 2019
28 Comments on Qt Customer Survey 2018
Posted in Biz Circuit & Dev Loop, Qt

The perpetual wheel of time turns, and 2018 is part of the past. For those of us not fortunate enough to have access to a DeLorean – fully equipped with Flux capacitor and a 1,21 GW power source – it is impossible to commit changes to this archived branch of time. What we can do, is to do a retrospect on 2018 and use the gained knowledge to improve during 2019. We are fortunate enough to have a lot of feedback provided by you in our 2018 Customer Survey, and it is about time we share some of the results with all of you.

Where’s Qt used?

Not surprisingly, Qt is still used in the same markets and industries as previous years, i.e. enterprise applications, game development tools, robotics, smart homes and factories, test and measurement systems, consumer goods, automotive, healthcare and medical equipment, security systems, digital TVs, aerospace and so much more. We know that Qt is used by some of the largest space agencies, but we still can’t confirm that Qt is in orbit or on its way to distant planets (I wanted to write galaxies, but that will most likely remain a dream for generations still).

Windows is by far the most common deployment platform, closely followed by a combination of Linux varieties and macOS. Deployment to Embedded Linux has increased with almost 10%, which confirms that the use of Qt in embedded devices is increasing. The fact that 20% deploys to mobile platforms (Android and iOS) is a good indication that we need to bring some more hay to those horses.

Technology and tools

User interface creation is one of the largest use-cases for Qt, and as such it is interesting to look at the use of the different UI technologies and how you use them. We have received a lot of feedback related to Qt Widgets, so let’s get that rabbit out of the hat first; Qt Widgets are not dead or dying. We are still putting a lot of time and effort into Qt Widgets, and that is time well spent. Even though the use of Qt Widgets is slowly declining (about 6% per year), 75% of you are still using them to create user interfaces. There will not be any radical changes to Qt Widgets, but they will remain functional and available for many years. We may even throw in a couple of new widgets we have been specifically asked for. Where the use of Qt Widgets slowly decline, the use of Qt Quick increases fast. The use has increased with 15% since 2017, and Qt Quick is now used in 2 out of 3 projects. The use-cases certainly vary depending on the target platforms; Qt Widgets are more frequently used for desktop applications and Qt Quick favoured for embedded and mobile platforms. The trend is, however, the same, the use of Qt Widgets are slowly decreasing while Qt Quick is rapidly increasing.

When it comes to tools, the short story is that the tools that were important for you in 2017, remained important in 2018. Qt Creator is still numero uno, and most of you love it. That being said, we will continue to improve Qt Creator based on provided suggestions, requests and reported bugs. Tools for debugging, profiling and static code analysis are increasingly important, and we get good feedback on these as well. There are some tools that clearly aren’t as useful and impressive, but the positive thing is that there is a good coherence between the tools you find important and the tools receiving most care and affection from our side.


Looking into customer surveys are – and should be – a humbling activity, but when it comes to the documentation it is hard to not go completely narcissistic. Close to 100% regard the documentation as a very important part of Qt, and when you get feedback like “I wish all documentation was like this” it is hard not to break out in a huge grin. A huge thanks to everyone who contributes, or has contributed to, the great piece of work Qt Documentation is.

Related to documentation are the various other forms of learning, finding information and discussing everything Qt. This particular blog post may not find a way to the stars (again dreaming of Qt, and myself, on the way to those galaxies) but in general, you find our blog posts interesting. This inspires us to continue the work and you can look forward to many useful blog posts this year. The forums are still relevant for many, but we would like to see more activity on forum.qt.io, making it even more relevant and valuable for all. Live webinars seem to be losing some of the appeal. On the other hand, recorded webinars, training videos and tutorials are in high demand. We will do our best to adjust to these trends.


It’s always important for us to learn the hows, whats, and wheres of your Qt usage, but equally (if not more) important is the feedback on your satisfaction. Every year we ask how likely it is that you will recommend Qt to a friend or colleague, rated on a scale from 0 to 10 (10 being very likely). We would have liked to see the same overwhelming feedback as for the documentation, but it gives us confidence when 35% respond with 10. If we group together 7 to 10, we have the feedback from 91,7% of you, so all in all we are pretty certain that you in general are satisfied with Qt. We know, from the survey and other channels, that there are many things and areas we can improve, and we will strive to do that in the coming weeks, months and years.

Thank you for taking the time to respond to our customer survey! This is but a brief summary of the results and the huge amount of valuable feedback received. We will continue to work with the collected data and utilise it to make Qt even better in the future.


Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Biz Circuit & Dev Loop, Qt


Philip Schuchardt says:

It would be nice if Qt Company got KDAB to fix their Qt3D documentation. Qt3D is great! But the documentation isn’t up to standard with the rest of Qt. Many classes have zero or minimal documentation.

Jakub Narolewski says:


AlGrenadine says:


Aurélien says:


Julien Bordes says:

What are the percentages of QNX 6.x and QNX 7.0 development platforms?

Julien Bordes says:

I meant deployment platforms

Harald Kjølberg Harald Kjølberg says:

The numbers for the different versions of QNX are unfortunately not available. However, the combined percentage for QNX is 3,5% for 2018, which is 3 times higher than 2017.

Konstantin says:

Over 15000 bugs says louder than words. It is not criticism but feedback that it is more important to maintain framework stable. Even most voted bugs are not fixed. If you face with issue with p2 it will probably never be fixed with current strategy.
The idea is to allow 3rd party contributors to fix bugs and reward them somehow.

Allan Jensen Allan Jensen says:

This is a topic we take very serious, but it is misleading to look at the total number of open bugs for a project this old. Instead look at the last 6 months: 3500 new bugs have opened but 6000 bugs have been resolved.

There have been issues with some modules not having had active maintainers for a few years, and the new maintainers appointed have a large technical debt to get through now, but overall bugs are currently being solved at a rate faster than they are opened.

ekke ekke says:

good to see that 20% are deploying to mobile platforms. You’re welcome to bring some more hay to those horses 🙂

jason says:

This could be even better if Qt’s mobile support was better. Qt still lacks some basic mobile functions that ReactNative, Xamarin, etc, can do. Qt can (and does) still work on these platforms, but you will end up writing native code. Whereas ReactNative et al, you won’t ever have to write native code (they wrap the APIs directly) but then you lose the platform Abstraction that Qt gives you. Qt could very easily be the best platform out there, but the native code aspect is really excruciatingly painful for those not on their usual platform. JNI sucks, and Objective-C sucks, and Qt doesn’t support Swift, so yeah… it’s a sheer drop in terms of enjoyment when you have to cross into the native land. I’d much rather deal with poor abstraction but wrapped all in the same language, than to not even have that. At least I can do an abstraction layer much easier if it’s all in the same platform.

Julien Bordes says:

What are the percentages of QNX 6.x and QNX 7.0 deployment platforms, where Qt is used?

John says:

Good to have more extensions for mobile platforms with native functions like notifications, native file and photo pickers, sharing etc

Brahim says:

I agree with John, because of these missing extensions I’m sure I’m not the only one to choose other techno than Qt for mobile, while I’m a fan of Qt.
I hope these modules will be added quickly: push notification, contact list, and others.

AlGrenadine says:


Francesco says:

I could not agree more,
however i don’t remember exactly when (world summit or another event)
Lars specifically said that for time being mobile platform won’t get any expansions.

Brahim says:

I do not know, but since Qt supports mobile if there were all these missing modules (which are essential for the mobile), I think Qt will be by far the best multiplatform framwork. except that with these gaps we are always obliged to go through native or other technologies ….
I hope they will change their minds and add these modules as soon as possible 🙂

jason says:


Richard says:

Just curious: Was Qbs part of the survey? Any results?

Stéphane says:

Hehe I though the same but didn’t want to open the troll… but now I’m also curious about the numbers we might have there !

Borgar Øvsthus says:


Philip Schuchardt says:


Harald Kjølberg Harald Kjølberg says:

Qbs was not part of the customer survey as such. The decision of deprecating Qbs was made before the survey was sent out, and Qbs was therefore not included. We did however receive comments about Qbs in connection with other questions. Some of these comments was asking for Qbs back, some saying that Qbs is the best build system and others saying that it is good to see that CMake will substitute Qbs. We knew that there would be reactions about discontinuing Qbs, and I think we all are entitled to an opinion about it. Qbs will remain supported throughout 2019 as previously announced, but the decision of going for CMake still stands. For those of you with a burning passion for Qbs; I am truly sorry that Qbs’s fate ended like this, but from a business perspective this made most sense. It’s probably of little consolation, but anyone willing can continue the development of Qbs.

John says:

There is a special place in the digital hell for IT-people who tries to fight with a progress (such as people who made a decision to go with CMake instead of QBS). Seriously, I think even QtCreator developers will curse them, when they will switch from QMake to CMake.

Richard says:

Thanks for clarifying.

Commenting closed.

Get started today with Qt Download now