3 ms·
I disagree with the author's assertion that the following point means you can't sell an app that uses the Netflix API: "charge, directly or indirectly, any fee
by drone 14y ago
I disagree with the author's assertion that the following point means you can't sell an app that uses the Netflix API:
"charge, directly or indirectly, any fee (including any unique, specific, or premium charges) for access to the Content or your integration of the APIs in your Application,"
It seems pretty clear to me that this point says that you can't add additional fees to include the Netflix API data in your app, or charge an additional fee to enable such a feature. Nowhere does it say that you can't charge for an app that includes the API.
However, that no enterprise-app statement is quite odd. I wonder what the specific driver was for that addition? There was likely some straw that broke the camel's back there, and it would be entertaining at the least (IMO) to learn what it was.
- fragmede 14y ago"charge... _any_ fee... for access... [to] (your integration of the APIs) in your Application," It certainly reads like that to me. (How else are you supposed to use the APIs in your application?)
- drone 14y ago"(including any unique, specific, or premium charges) for access to the Content or your integration of the APIs in your Application" Is the actual text, the part you added was your interpretation of the meaning - however, there are some indicators (starting with the parenthesized text in the original) which imply you're reading it overly broad. "For access to the Content" (the Content being the content served by the API), and "or your integration of the APIs". Nowhere does it say, "You may not charge any fee for any application which accesses these APIs," which if it were the intent of the lawyers to ensure that only "free" applications used the APIs, they would've stated so. Instead, they talk about fees for accessing the content and fees for integration, which seems to be to be clear that they are indicating that they don't want people selling the content served by the API or charging extra for using the Netflix API.
- fragmede 14y agoThe word 'any' precedes the parenthetical statement which I take it to mean, well, any. You are free to interpret the word 'any' however you'd like. I must say though, I do like your interpretation more. :) From http://developer.netflix.com/page/Api_terms_of_use http://developer.netflix.com/page/Api_terms_of_use, section 1.9: 1.9 Appropriate Conduct and Usage Restrictions. You are responsible for your own conduct while using the API and for any consequences thereof. You will use the API only for purposes that are legal, proper and in accordance with these Terms and any applicable policies or guidelines provided by Netflix from time to time. In addition to the other restrictions contained in these Terms, you agree that when using the API, you will not do the following, attempt to do the following, or permit your end users or other third parties to do the following: ...charge, directly or indirectly, any fee (including any unique, specific, or premium charges) for access to the Content or your integration of the APIs in your Application, or use the APIs to build an enterprise application (e.g., that you distribute to other companies);
- SoftwareMaven 14y agoI completely agree. Don't make Netflix an in-app purchase after-the-fact. I think the enterprise clause is to prevent companies from selling software to do analytics against the Netflix DB. Netflix wants that pie. The problem is that can become a very gray area.