> Can I publish an application that does not use Apple IP, let’s say something written in ARM assembler? Or am I forced to use Apple IP?
Not sure what you mean by forced to use Apple IP. You are running on their ARM chip under their kernel, using their libraries to read touch events and display to the screen.
IP is incredibly broad; you can't really avoid using say all copyrighted libraries.
If you are speaking toward is there a path to write applications which will work on iOS devices without signing agreements, paying royalties or having legal action taken against you, there's the Safari browser and it sounds like there will be many more web browsers soon.
> I can publish on windows without using Microsoft IP, I can publish on android without using google IP, right?
I don't see how you could publish a legitimate app for Windows without using e.g. ReadFile.
I don't know how you would publish an Android app without using its proprietary manifest file; you probably come closest there to a minimal working application due to instead using lots of Oracle IP.
iOS would not run code which is not built and signed by their tools.
Unless EU mandates the minimal interoperability requirements. You do not pay if your app is a Web app, so maybe better interop with web apps mandated would be more interesting (like allowing to add icons for these apps).
Using APIs is fair use. If you can avoid using Apple code to do so, or only minimal ones, like headers, then I think you would be in the clear. See Google vs Oracle. IANAL of course and personally I wouldn't pursue this.
In the EU there's a "Computer Programs Directive" which grants us the right to go as far as to reverse engineer any licensed software for the purposes of interoperability.
Reverse engineering APIs is fair use, not simply using APIs. Eg when Google implemented their own implementation of Java APIs, that was deemed fair use. Google only copied the interface. The courts ruled you can build a competing product that copies an interface for compatibility, just like Compaq did with IBM’s BIOS. Google absolutely would have been on the hook had they used Oracle’s implementation of the APIs.
Not sure what you mean by forced to use Apple IP. You are running on their ARM chip under their kernel, using their libraries to read touch events and display to the screen.
IP is incredibly broad; you can't really avoid using say all copyrighted libraries.
If you are speaking toward is there a path to write applications which will work on iOS devices without signing agreements, paying royalties or having legal action taken against you, there's the Safari browser and it sounds like there will be many more web browsers soon.
> I can publish on windows without using Microsoft IP, I can publish on android without using google IP, right?
I don't see how you could publish a legitimate app for Windows without using e.g. ReadFile.
I don't know how you would publish an Android app without using its proprietary manifest file; you probably come closest there to a minimal working application due to instead using lots of Oracle IP.