Nokia and Qt

nokia.gifNokia reached a significant milestone today. However, more recent events at Nokia have turned something that would have been very significant into something very few people will care about.

What I am talking about is the release version of Qt SDK 1.1 and more importantly the possiblity to publish applications on Ovi that make use of Mobility 1.1 (i.e. significant useful device APIs). As long ago as December 2009, I was declaring Qt not fit for commercial use. Since then, there have been so many promises, announcements and tech previews but no way to publish a Qt app that uses significant device APIs. Today is the day that Qt becomes technically viable for many projects. What’s more, it now includes a release version of QML that provides a much easier Javascript-esque Qt development environment rather than having to use c++. Unfortunately, all this is less exciting now due to Nokia’s new strategy.

What can we all learn from this (Qt)? Release less, but more often. Analyse the technical aspects deeply before assuming ‘buying in’ a solution will dovetail with your needs. Think about timing. Particularly think about dependencies. Qt depended on future UIs that theselves were uncertain. If you fail, be flexible and think how things might be re-purposed.