Browser based on WebKit/safari but with chrome extensions support

In theory, you’d simply write a cross-platform browser extension using the WebExtensions API.

In practice, publishing it to the App Store is prohibitively expensive compared to the Chrome Web Store, and Safari has a much smaller user base 🥲

In theory, you’d simply write a cross-platform browser extension using the WebExtensions API.

In practice, publishing it to the App Store is prohibitively expensive compared to the Chrome Web Store, and Safari has a much smaller user base 🥲

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions

This is how you’d currently go about porting a Chrome extension to Safari:

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

This is how you’d currently go about porting a Chrome extension to Safari:

https://developer.apple.com/news/?id=qiz0arxc

Hmm, come to think of it — since Tauri’s webviews are Safari WebKit-based, it wouldn’t seem too far-fetched for someone to re-implement the WebExtensions spec in a way that doesn’t rely on the App Store.

Hmm, come to think of it — since Tauri’s webviews are Safari WebKit-based, it wouldn’t seem too far-fetched for someone to re-implement the WebExtensions spec in a way that doesn’t rely on the App Store.

https://v2.tauri.app/reference/webview-versions/