[OS] Run and Install Chrome extensions in Safari
problem: extensions in safari cost annual money to create because of that most extensions from chrome are missing. on top of that, safari works differently with different apis than chrome. because the lack of extensions in safari people…
A concise extract from the original post, kept together with the community response below.
“problem: extensions in safari cost annual money to create because of that most extensions from chrome are missing. on top of that, safari works differently with different apis than chrome. because the lack of extensions in safari people…”problem: extensions in safari cost annual money to create because of that most extensions from chrome are missing. on top of that, safari works differently with different apis than chrome. because the lack of extensions in safari people use chrome instead which isn't designed for macOS like safari.
on top of that even if you try creating an extension it will fade after ~week with a free apple account, I made a system that renews and updates your extensions for you.
I created Viaduct for people who want to run chrome extensions but their main browser is safari or people who use chrome for the extensions.
apple has a similar feature for developers that convert chrome extensions to safari extensions but apple's version doesn't handle missing apis, meaning more complex extensions will break and won't work, Viaduct has an open source engine called viaduct cli that creates solutions for those missing apis so even complex extensions can work.
The app is free for testing 2 extensions without extensions renews and updates The paid version is 19$ with unlimited extensions auto renews and updates The cli version is free and open source for everyone but without GUI and without auto renews and updates. Use code "3LABNWV" for -10%
Download the App here: https://magicelklabs.com/viaduct Download the CLI here: https://github.com/magicelk235/Viaduct-CLI
about me: Linkedin: https://www.linkedin.com/in/magicelk235 Github: https://github.com/magicelk235 Personal Mail: [yehonatan.2350@gmail.com](mailto:yehonatan.2350@gmail.com)
App Source: https://github.com/magicelk235/Viaduct-app Website: https://magicelklabs.com Support Mail: [support@magicelklabs.com](mailto:support@magicelklabs.com)
Collected discussion
10 collected
Comments are shown in source order. Reply indentation appears only when the scraper captured a parent relationship.
Price to high also with discount.
How does this work under the hood?
https://www.reddit.com/r/Safari/comments/1uy08r5/chrometosafari_convert_sign_any_chrome_extension/
the part i would want very clearly documented is the compatibility boundary. converting/signing is one thing, but the messy failures usually come from extension APIs Safari does not expose or permission flows that behave differently. a public tested extensions list with works / partial / broken would probably answer half the trust questions before people install it.
the engine is a static transformer plus a compat shim, viaduct runs once you point it at a chrome extension, it rewrites the source and packages it as a safari web extension, It's not sitting in the runtime
if you are a developer and prefer cli you can always use the cli version for free https://github.com/magicelk235/Viaduct-CLI
You can test it using the CLI (unlimited) or the free tier of the app version(twice). The Chrome Web Store has countless extensions, and the extensions installed by users will vary greatly. It's quicker to just try it out.
yeah, trying it yourself is the fastest answer for one extension. i still think a tiny compatibility page would help a lot, even if it starts with 20 popular extensions. people mainly want to know whether failures are hard Safari API limits vs a setup issue. even a simple works / partial / broken list with notes like 'background service worker issue' or 'permission prompt differs' would make testing feel less random.
I only have 4 or 5 that don't really have a native safari equivalent. I'll look at your project more closely at some stage. Thanks for the feedback
If you can find out what the extension uses to run on it from the Chrome Web Store, you should do that. But, I don't think that's something individual developers should be doing. If you think that's the right thing to do, why not start by not only testing the extension you want to use, but also analyzing the test results and communicating them to the developers? If you think it's necessary, you have a responsibility to cooperate. Unless you're just saying it on a whim and trying to push your own responsibilities onto others, you should take responsibility yourself. That's clearly a more efficient task if each user reports it on a system like a wiki. Developers should be focusing on improvements only they can make or developing other apps.