4 ms·
So... This last year in Safari Extension world: * $100 buy in. Yearly. (Firefox, Edge, Chrome, Opera... No license fees.) * Long, bug-prone, and somewhat idio
by shakna 10y ago
So... This last year in Safari Extension world:
* $100 buy in. Yearly. (Firefox, Edge, Chrome, Opera... No license fees.)
* Long, bug-prone, and somewhat idiotic review process.
* No way to charge for an extension, to recoup that $100. So its ads or nothing.
* Installation page only. No reviews. No real information.
Caveat: You can develop for free, without getting listed, but then you can't automatically update the extension.
What's coming in Safari Extension world:
* The $100 fee is staying.
* Xcode requirement. You'll need a Mac to publish.
* Swift/Objective-C requirement. No more HTML/JS/CSS only.
* Mac store listing, which means you can charge for extensions. But the Mac Store isn't known for a nice review process.
* Hugely lacking documentation. Hopefully this'll change... But Apple doesn't have a good track record here.
Result:
Reddit Enhancement Suite has to decide between not publishing for one of the major browsers, or paying out for a longer, harder to maintain process, to achieve the same thing as they already do for Firefox, Chrome, Edge and Opera.
Personal anecdote:
Apple seems to hate their own developers. This story, others, and my own experiences tell me that Apple makes everything more difficult than need be to put together a program, small or large, that actually runs on their platform.
Swift was a step in the right direction, a nice language, a decent Open Source effort, and cross platform to boot.
But Safari... Safari lacks in so many areas that it's progress on JS doesn't matter much. Isolating those who build for it is unhelpful.
It almost seems like Apple want Safari to die.
- bangonkeyboard 10y ago> Caveat: You can develop for free, without getting listed, but then you can't automatically update the extension. There's a comment on the post disputing this possibility.
- shakna 10y agoTrue, I guess one could concievably build your own update mechanism. But that's even more overhead than what is necessary for all the other browsers, who let you use their stores and update mechanism for much less than $100/developer/year.
- bangonkeyboard 10y agoSorry, I should have been specific: a comment on the Medium post that is TFA: This isn’t correct. Without paying the $100, you can’t get a certificate, and without a certificate, you can’t sign an extension to build a safariextz.
- shakna 10y agoSo the situation is even worse than I thought? I mean, it is technically possible to install untrusted extensions, using xcode's self signing, but it isn't exactly straight forward and/or easy.
- coldtea 10y ago>So the situation is even worse than I thought? Or even better? Higher barrier to entry and more protection against crappy extensions, spam extensions, amateur hour, etc?
- bangonkeyboard 10y agoXcode is used for Safari App Extensions. Safari Extensions like RES are created in Safari's Extension Builder, which apparently balks without a signing certificate.
- onion2k 10y ago$100 buy in. Yearly. (Firefox, Edge, Chrome, Opera... No license fees.) There's a one-off $5 fee to publish things on the Chrome store.[1] [1] https://developer.chrome.com/webstore/publish#pay-the-developer-signup-fee https://developer.chrome.com/webstore/publish#pay-the-develo...
- shakna 10y agoYou're right. But that one off fee seems incredibly negligible against Safari's fee, which is 20x larger... And yearly. For smaller marketshare.
- Drakim 10y agoYeah, Chrome's fee seems more like a gate-keeping cost to ensure that the store doesn't get spammed or abused, not an attempt of Google by generate revenue.
- cageface 10y agoSwift is a nice language and I applaud all the hard work that people at Apple have put into it. In almost every other respect developing for Apple platforms feels like a marriage to an abusive and indifferent partner. Coding for Android or the web can be frustrating too, of course, but a lot of the complexity there is inevitable given the decentralized nature of those platforms. Apple controls the entire software and hardware stack so their crappy dev experience is a consequence of either incompetence or arrogance.
- pavlov 10y agoApple seems to hate their own developers. This story, others, and my own experiences tell me that Apple makes everything more difficult than need be to put together a program, small or large, that actually runs on their platform. To Apple's credit, they are occasionally way ahead of the curve on developer convenience, and have reaped huge benefits from that. I tried making smartphone apps in 2003-07 for Symbian, Java ME and the very first Android beta (the one that had a traditional keypad phone emulator). The experience was always disheartening. Horrible IDEs that sometimes cost money, awful device feature fragmentation with no standard ways to handle it, inconvenient APIs designed in the style of '90s embedded platform expectations. If you managed to get a working app together, distributing it was a mystery. On Symbian, you'd have to pay something on the order of $1000+ for certification from a "special Symbian partner", and even after that there was no central app store. There were websites offering downloads (and paid listings), but users would not stumble on those. It was a terrible offering all around. The native iPhone SDK in 2008 changed all that. Suddenly there was a smartphone with a desktop-class IDE experience and desktop-derived APIs, with easy access to fascinating new multitouch UI possibilities... And there was an integrated Apple-curated store where you could publish any number of apps for only $99 / year! That was an amazing deal compared to anything that came before in this space. Some occasional hassles with Xcode bugs and certificate weirdness was nothing compared to the nightmare of the Symbian/JavaME style mobile dev experience. Even before that, Apple had done well by its Mac OS X developers by offering the NeXT-originated Cocoa tools for free. Back in 2001, that wasn't the expectation yet. It was a good API, battle-hardened at NeXT already, and much better than anything Microsoft was pushing in that Windows XP timeframe. Apple's efforts to support OS X development had two major benefits: the Mac's resurgence was helped by increasing availability of good 3rd party software created by dedicated developers, and the iPhone global launch was greatly helped by the fact that those same OS X developers were able to easily move to the iPhone.
- JohnTHaller 10y ago> Reddit Enhancement Suite has to decide between not publishing for one of the major browsers, or paying out for a longer, harder to maintain process, to achieve the same thing as they already do for Firefox, Chrome, Edge and Opera. Just stop supporting Safari. It's more trouble than it's worth and, generally, the type of person that runs RES isn't running something has uncustomizable as Safari.
- falcolas 10y agoI was, up until recently, running Safari as my main browser just to avoid the cost in battery life; I'm also an avid RES user. I finally bit the battery life bullet and moved to Firefox for my personal browsing, but it was a hard choice to make. The battery savings (until recently) were non-trivial; giving those up was a hard decision.
- kitsunesoba 10y agoIt depends on what facets you're speaking of, but some parts of Safari are more customizable than equivalent parts of Chrome. Safari still allows you to customize your toolbar, for instance, which unless my memory is failing me was never an option in Chrome. Of course Firefox beats both Chrome and Safari out in this aspect, but you trade off things like the battery life you mentioned as well as compatibility with OS X services and general native-ness (Firefox has always felt odd and foreign under OS X due to using XUL for its UI). For someone like myself whose extension needs stop at Stylish and a good adblocker, the trade off isn't worth it.
- matthewmacleod 10y agoApple seems to hate their own developers. This story, others, and my own experiences tell me that Apple makes everything more difficult than need be to put together a program, small or large, that actually runs on their platform. Totally disagree. Publishing Safari extensions might be a rubbish experience, but publishing anything else is fine.
- Twirrim 10y agoYears and years of anecdotes about the app store submission process would suggest otherwise.
- benologist 10y ago* Swift/Objective-C requirement. No more HTML/JS/CSS only. It almost sounds like they want really fast extensions they can confidently distribute on iOS...
- cheshire137 10y ago> Firefox, Edge, Chrome, Opera... No license fees. I think Google charges like a $5 one-time fee to publish a browser extension, as a way of discouraging trash extensions.
- Eridrus 10y ago> * Mac store listing, which means you can charge for extensions. But the Mac Store isn't known for a nice review process. Do you know if this will allow companies to install extensions to their employee computers automatically? I worked on a commercial Safari extension briefly assuming this functionality had to be there, but gave up when I realised there was no way to push it to an employee's computer without a prompt.