3 ms·
There's no drama here. The oldest copy of the current app store guidelines I could find goes back to 2014: http://web.archive.org/web/20140903022336/https://d
by bdcravens 7y ago
There's no drama here.
The oldest copy of the current app store guidelines I could find goes back to 2014:
http://web.archive.org/web/20140903022336/https://developer.apple.com/app-store/review/guidelines/ http://web.archive.org/web/20140903022336/https://developer....
"2.5 Apps that use non-public APIs will be rejected"
However this has been known dating back to 2010, so I'm sure someone can dig up an older version of the agreement that says as much.
The fact that Electron is a much easier way to build apps than Swift, Obj-C, etc has nothing to do with the enforcement of these long-standing rules.
- fortran77 7y agoWhy does Electron need to use non-public APIs?
- bdcravens 7y agoMy understanding is that it's Chromium that uses these (ostensibly for performance), not Electron, but Chromium is a dependency of Electron.
- lostmyoldone 7y agoAccording to a previous poster, the public API cause excessive power drain and is a fair bit slower. Since Apple usually use the argument of how the OS and API's are built to draw less power, it's quite peculiar that they can't find a more constructive solution than threatening to ban people and companies from the app store.
- ken 7y agoI think half the drama is that there are Electron apps in Apple's app stores already, e.g., a quick grep of Slack.app shows it contains all of these symbols in "Electron Framework.framework", yet it was apparently approved. Is this another case where you can break the rules but only if you're rich enough?