Hacker News Reader

The license is the critical feature: the open source version is available under GPL and LGPL. Beware of the implications for iOS development with GPL/LGPL (have to distribute source or .o files for your application).

Ok. So if you contribute to the project, you assign copyright of your code to Digia who then dual-license the project to end-users under the GPL/LGPL and for a fee, a commercial license to use it in proprietary applications. Makes sense.

> have to distribute source or .o files for your application

Not if you dynamically link

Do iOS guidelines allow dynamic linking?

AFAIK it's not allowed, so Qt commercial is actually the only option for non-OSS on iOS.

The iOS and Android part is privative. There are open source approaches to do the same, but they don't share code, and use different technology, as far as I remember, the Open source one uses Dalvik while the other not in Android for example.

The only difference is support I believe.