
If someone who is knowledgeable with writing Safari Extension Apps, or even better, making an existing WebExtension somehow work with Apple's new API, wants to provide some consulting on how we can bring Bitwarden back to Safari, please let me know. Maintaining a completely different browser extension codebase for that many users isn't feasible.įor someone who is not well versed in the Apple development ecosystem, Apple's documentation and other community resources on writing Safari Extension Apps (the new way) is pretty sparse

Safari currently accounts for <2% of our browser extension users. Safari, Firefox (opens in new tab) and Edge (opens in new tab) alongside more obscure options like Vivaldi, Brave, Tor.

Apple's new way requires re-writing the extension interface and backend using native Swift/Objective-C. Bitwarden Review: Pros & Cons, Features, Ratings, Pricing and more. All other browsers use a standard way of writing extensions (called WebExtensions) with web technologies like HTML, JavaScript, CSS. As far as I understand, this means that we cannot use our existing browser extension code any longer. I am not sure we will be able to continue supporting Safari in the near future.Īpple has introduced a completely new way of writing extensions for Safari.
