3 ms·

Nothing you have described would be disallowed. Often the ideas about restrictions are simply false beliefs.

• jedberg 6y ago
  Of course they would be. OP said they wrote their own browser. The app store specifically disallows this. You must use the Safari render engine.
  • zepto 6y ago
    > headless browsers available. So I wrote half of my own browser The OP said - headless browser, I.e: network and parsing the Dom, but not rendering. Perfectly allowed. Please stop saying otherwise.
  • FlownScepter 6y ago
    This is just wrong. Apple disallows apps that duplicate existing functionality, i.e. browsers. You can write whatever wack headless browser you want, and there are tons of frameworks for this exact purpose, too: All manner of methods to do network things without invoking Safari. This is a jawbreaker of hyperbole around a chewy gum center of truth.
  • xxs 6y ago
    Rendering engine is not the issue. It's the JIT - firefox could publish a browser, it would just need to have interpreted javascript and it'd be useless.
    • benibela 6y ago
      Well, then it is good, I did not make a JIT (only XPath AST, not even bytecode) Although I have been thinking about making a JIT. Building on for x86 is easy enough, but then it is useless for ARM. I would not want to build two JITs. Or four with 32/64-bits.
      • zepto 6y ago
        If you needed Jit for JavaScript there is nothing on iOS stopping you from using JavascriptCore.