4 ms·
I agree it was only a matter of time, the previous arrangement was pointlessly arcane. But make no mistake, Apple still wants to remain firmly in control. The
by tialaramex 6y ago
I agree it was only a matter of time, the previous arrangement was pointlessly arcane. But make no mistake, Apple still wants to remain firmly in control.
The development of these extensions is eased, but you still need to pay Apple tax to give them to users. If your extension generates revenue maybe that's fine. If it doesn't Apple is asking you to give them money so that you can help their users, how about No?
- bredren 6y agoI don’t know if it was arcane so much as it was very conservative in what it allowed. Browser extensions can seek very wide permissions and are extremely powerful because they can automate requests from a user’s IP address. I’d guess Apple only did this because they had to.
- deleted 6y ago[deleted]
- Razengan 6y agoYou can publish free extensions, as long as you have a developer account. Since the account costs $100 a year, this makes more sense for apps who want to offer a Safari extension, e.g. a Japanese learning aid with a website translation extension.
- ksec 6y agoYes and that is why a lot of extensions cost money on Safari, while the Chrome and Firefox counterpart are free.