We use the native SDK to provide POD support in our AR app and platform - see www.zappar.com. It’s a great format, and the SDK is really useful, so thanks very much for that. I’m sure our usage in Zappar is compliant with the license agreement (we list the required acknowledgement in our documentation).
There are a few things that are not 100% clear though. We provide an embeddable component for third parties to include in their apps. This is provided in compiled binary form, and contains our complete content platform, a small part of which is the POD rendering support including code derived from the PVRTools SDK. Can you confirm that this usage is allowed under the license agreement, providing the third-party app developer includes the required attribution with their app?
The term 2)b)ii) is a little confusing:
- […] Imagination grants to you a non-exclusive, non-assignable licence to:
[…] (b) distribute the SDK in source code, object file, or compiled binary form as a component of your application, provided that:
ii. you distribute such components under terms no less restrictive than those in this Agreement;
I don’t quite understand how that requirement can be met in general. Clearly any app on the app store is distributed under the terms of the user EULA that users must agree to before they are able to use the store at all. It is almost certain those terms are more restrictive than the SDK EULA. However the FAQ appears to be clear that the intention is the SDK can be used to build commercial apps without fee, as long as attribution is given.
I suspect that the 2)b)ii) is referring more to source distributions, but it would be nice to have clarification that as long as the correct attribution is provided (a) people can safely use the SDK as part of commercial apps in general, and (b) that we can provide a compiled versions to a third party as part of a larger binary library which they can then incorporate into their app.