In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…
I agree with your point on a whole, I do want to add that tamper monkey does indeed work on Safari so you could just add that line of JS there
Safari 14 added WebExtensions support, so where are the extensions?
21–30 of 224 posts
Re: Safari 14 added WebExtensions support, so where are the extensions?
#22In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…
Do you know why the app did not appear in Safari’s preferences? And how did you fix it?
Re: Safari 14 added WebExtensions support, so where are the extensions?
#23I wonder if the bigger hurdle here is that you have to spend money to get into the developer program (unless this is waived for these kinds of apps, I couldn’t tell when trying to dig up an answer) I don’t know that effectively slapping an app shell around an extension is a big hurdle, but no other web extension store charges for entry, so that very well could be the real barrier here.
Yeah. The $99/year is big enough to pretty much block out all hobby devs and open-source projects, so what's left are generally commercial and closed-source. Apple says that they do their own vetting of extensions, but I don't trust Apple to prevent extensions from reading my browsing history, especially considering spyware extensions like Honey are served on the App Store without warning.
You have to explicitly grant permissions as a user for safari extensions.
Re: Safari 14 added WebExtensions support, so where are the extensions?
#24Re: Safari 14 added WebExtensions support, so where are the extensions?
#25In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…
That's better suited as a userscript.
Re: Safari 14 added WebExtensions support, so where are the extensions?
#26I tend to not trust extensions otherwise and would really prefer Safari to have built in total ad blocking - zero tolerance for any ads at all.
Re: Safari 14 added WebExtensions support, so where are the extensions?
#27We have uBlock origin and many others extensions working already. By doing this we get best of both worlds - performance and energy use of Webkit and extensions from chrome/firefox.
Screenshot: https://ibb.co/7V8sfyX
We are open for beta testers. Please email me if interested with short background and area of your interest.
Re: Safari 14 added WebExtensions support, so where are the extensions?
#28We are working on a new native macOS browser based on Webkit with native web extension API support built in. We have uBlock origin and many others extensions working already. By doing this we get best of both worlds - performance and energy use of Webkit and extensions from chrome/firefox. Screenshot: https://ibb.co/7V8sfyX We are open for beta testers. Please email me if interested with short background and area of…
Re: Safari 14 added WebExtensions support, so where are the extensions?
#29Each uses a separate URI scheme.
So Chrome uses chrome-extension:
Firefox uses firefox-extension:
... etc.
which means web extensions for Firefox won't work with Google Firebase because they only support chrome-extension.
Why the heck isn't it web-extension: ???
Re: Safari 14 added WebExtensions support, so where are the extensions?
#30And, for the content blocker extensions market, there’s essentially no point in releasing it as a paid web extension for iOS/macOS users, because there’s already better paid app competitors that do this, like 1Blocker or Guardian VPN or etc, that are full native apps on the platform with the appropriate hooks to be performant and such.
Therefore: What valuable browser extension ideas other than content blockers exist, that could have any significant user base and value, that isn’t already met by better and more capable native apps on macOS and iOS, and somehow could charge people money for the extension with their willing cooperation? They’d obviously have to use a subscription model, so factor that into consideration when assessing the market.
I’m unable to come up with anything that would make this segment of the App Store market worth my time to invest code into, and I already have a developer account for other reasons, so I don’t even have the annual fee barrier to consider. I remain hopeful that I’m wrong, but no one’s made a convincing argument yet. Prove me wrong, HN.
(I see most people taking the “wrap WebKit” route instead, which makes more sense since it provides the capabilities an extension can’t offer, and is dead simple by virtue of the platform’s capabilities. Makes more sense to me, anyways, and then too. So: now what?)