Windows, Linux, OSX, yes, if you're writing a desktop app. That's what Qt is good at.
But Android? On devices with a completely different form factor, input schemes, and resource requirements? I don't think that is feasible, particularly from a user experience point of view.
It is absolutely feasible. Meego and Symbian devices habe about the same form factors, input methods and resource constraints and Qt works like a charm on those. It's just that few people have actually seen how well Symbian works these days.
I was responding to the claim that: "a single Qt app can run on all of those platforms with minimal modification".
And having ported a fairly successful iOS app to Symbian^3 (using mostly Qt Quick/QML), I would seriously contest the claim of 1) Qt working like a charm on Symbian and 2) how well Symbian works in general.
How is that not feasible? What makes Java innately more capable of handling varying form factors than C++ and Qt?
I'm not saying that Java is either.
Rather, that to provide the best user experience on each different type of device (i.e. to follow platform conventions and paradigms and take advantage of unique device capabilities where present), it's best to use platform specific tools and design your application to be consistent with the expected user experience for that particular device.
That being said, we already knew Nokia was going to dump it, they already sold off the commercial support and licensing division and made a shallow claim "we're going to continue contributing to Qt," which almost always should be read by adding "until..." at the end.
I'm happy to see Qt back in the hands of someone who cares about it. Personally, I'm not much interested in whether or not Nokia plays in the sandbox.