undefined | Better HN

0 pointslapcat7mo ago0 comments

This is a bit misleading. Safari content blockers have been available on iOS since 2015. In 2021, JavaScript-based Safari web extensions were added.

0 comments

karel-3d7mo ago

Trying to actually write one before, it's incredibly frustrating experience, as you still need to have some weird native glue code in in Swift/Obj-C. And everything is under-documented, as it the true Apple Experience. (I forgot the details. I can find the code on github, maybe.)

If you ask yourself why there are so little Safari extensions, this is why.

edit: I look at the code now... I needed to wrestle with BOTH cocoapods and npm, at which point I gave up

darrenf7mo ago

[EDIT to clarify: here I’m talking about writing a javascript based extension, not a content blocker]

That’s not my experience (in the admittedly only browser extension I’ve ever written).

After getting it working to my satisfaction in Chrome and Firefox, I created the Safari macOS/iOS versions by running

    $ xcrun safari-web-extension-converter --bundle-identifier <bundle ID> .

in my repo. Then I opened xcode, configured the signing/capabilities, and built it. IIRC I had to create the directory for the output because xcode didn't do it itself, but once that was done I could install it to both macOS and iOS. Honestly I was surprised it was so little effort. I don’t doubt that an extension with more functionality than mine might require a jumping through a lot more hoops, but it definitely can be easy to successfully target Safari IME.

karel-3d7mo ago

Interesting. Maybe I tried to do something too complex, I don't remember.

https://developer.apple.com/documentation/safariservices/cre...

Here they talk about the "container" that needs to be in Swift/Obj-C. I remember I used to have some problems with the "container" application

I think the issue starts to be when you want your extension/app to have any kind of settings that is retained? I don't remember, really.

1 more reply

ErneX7mo ago

Even better, thanks for the correction.

j / k navigate · click thread line to collapse

0 comments

karel-3d7mo ago

If you ask yourself why there are so little Safari extensions, this is why.

edit: I look at the code now... I needed to wrestle with BOTH cocoapods and npm, at which point I gave up

darrenf7mo ago

[EDIT to clarify: here I’m talking about writing a javascript based extension, not a content blocker]

That’s not my experience (in the admittedly only browser extension I’ve ever written).

After getting it working to my satisfaction in Chrome and Firefox, I created the Safari macOS/iOS versions by running

    $ xcrun safari-web-extension-converter --bundle-identifier <bundle ID> .

karel-3d7mo ago

Interesting. Maybe I tried to do something too complex, I don't remember.

https://developer.apple.com/documentation/safariservices/cre...

Here they talk about the "container" that needs to be in Swift/Obj-C. I remember I used to have some problems with the "container" application

I think the issue starts to be when you want your extension/app to have any kind of settings that is retained? I don't remember, really.

1 more reply

ErneX7mo ago

Even better, thanks for the correction.

j / k navigate · click thread line to collapse