Mac App Store & licensing
-
Hi all,
I currently consider using Qt 6 to write an application that also should be released in the Mac App Store later on then. Qt's cross-platform capabilities are still superior.
The application should be closed-source and be capable of in app purchases (this is possible as far as I've seen https://doc.qt.io/qt-6/qtpurchasing-appstore.html).
Still what tempers me the most is that I do not understand which license I am able to use. I am a single developer, which would not mind buying any Qt commercial license but still my app idea is in babysteps. So there is no possibility to invest that much in a product that could fail.
I have always used Qt open-source for any of my open and closed source apps on Windows, dynamically linked to Qt as well as the possibility to replace the libraries found.
How is that procedure when pushing to the Mac App Store? I would still dynamically link but I think it is not possible to simply replace Qt in that bundle and hope for the best (as a user).
Would this make me applicable to still use the open-source version or do I really need a commercial one?
And yes, best would be to talk with a lawyer. Still asking for some input here.
Many thanks!
Jan -
@nitro0 said in Mac App Store & licensing:
I am a single developer, which would not mind buying any Qt commercial license but still my app idea is in babysteps.
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
-
@nitro0 said in Mac App Store & licensing:
I am a single developer, which would not mind buying any Qt commercial license but still my app idea is in babysteps.
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
I would still dynamically link but I think it is not possible to simply replace Qt in that bundle and hope for the best (as a user).
You can provide separate binary / app bundle for customers who request it, without notarization etc. Then they can swap the libraries and run the app, it should work.
-
@nitro0 said in Mac App Store & licensing:
I am a single developer, which would not mind buying any Qt commercial license but still my app idea is in babysteps.
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
@SimonSchroeder said in Mac App Store & licensing:
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
Is this true? Even if I just develop locally and shortly before release I am going to switch? This would be mindblowingly weird.
-
I would still dynamically link but I think it is not possible to simply replace Qt in that bundle and hope for the best (as a user).
You can provide separate binary / app bundle for customers who request it, without notarization etc. Then they can swap the libraries and run the app, it should work.
-
@SimonSchroeder said in Mac App Store & licensing:
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
Is this true? Even if I just develop locally and shortly before release I am going to switch? This would be mindblowingly weird.
@nitro0 said in Mac App Store & licensing:
@SimonSchroeder said in Mac App Store & licensing:
The Qt Company does not like you first developing with the open source license and then later switching to a commercial license. You have to decide that from the start.
Is this true? Even if I just develop locally and shortly before release I am going to switch? This would be mindblowingly weird.
Yes it is true and yes it is weird.
The problem here is Apple and it's signing process.. I could imagine if you simply swap libraries this won't work..
You need to provide a way for your customers to swap the libs & make the app work. This will surely not work with signed app from the store. But if you provide the unsigned binaries / app bundle to them (upon request or on your website), then they can swap and run (outside of the App Store). We are talking about macOS, so running unsigned bundles is still allowed here.
I think this is still OK license-wise.
