3 ms·
I am not a license expert- but I am pretty sure if you can only release your app as GPL (either it requires a GPL component you did not write or you are unwilli
by jmount 17y ago
I am not a license expert- but I am pretty sure if you can only release your app as GPL (either it requires a GPL component you did not write or you are unwilling to release it non-GPL) then you can not make it an iPhone app (Apple seems to be hostile to this). In principle there is nothing wrong with charging for GPL apps, so if it wasn't for Apple's license issues you would be fine. However, if you wrote the app yourself (or somehow own it) then there is nothing in the GPL preventing you from releasing a non-GPL version on the iPhone app store (dual licensing).
- roschdal 17y agoOk. The code has to be GPL licensed, because the webapp is based on an existing GPL codebase. Do you have any other suggestions for a business model? Alternatives to the iPhone app store? Should I try the Android Market?
- jmount 17y agoActually now I wondering. It looks like GPLv3 is not compatible with the iPhone (the anti-Tivo clause: http://www.fsf.org/blogs/community/why-free-software-and-apples-iphone-dont-mix http://www.fsf.org/blogs/community/why-free-software-and-app... ) but I am less clear if GPLv2 is incompatible (or if people just hope it is, see: http://www.geoffeg.org/wordpress/2009/10/07/the-iphone-and-the-gpl-v2-are-not-incompatible/ http://www.geoffeg.org/wordpress/2009/10/07/the-iphone-and-t... ). So you may want to look a bit deeper into the license of the library you are using (LGPL, GPLv2, GPLv3 ...).