Metamask-extension: wheres the safari metamask extension?

[markmark1]

wheres the safari metamask extension?

[bdresser]

Hey @markmark1 - Safari doesn’t use the WebExtension protocol like every other browser does. To build an add-on for Safari would require a lot of browser-specific work that we haven't prioritized yet.

In the meantime, try Chrome 😄

[markmark1]

Chrome is slow and heavy electron app
Pls do safari plugin if possible

On Sep 7, 2018 at 12:21 PM, bobby dresser [e-mail] wrote:

Hey @markmark1 https://github.com/markmark1 - Safari doesn’t use the
WebExtension protocol like every other browser does. To build an add-on for
Safari would require a lot of browser-specific work that we haven't
prioritized yet.

In the meantime, try Chrome 😄

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MetaMask/metamask-extension/issues/5173#issuecomment-419539971,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGHom0WPZmQO8nnITPnxeXeCH2RJ_Bn1ks5uYsdNgaJpZM4WT-u6
.

[bdresser]

@markmark1 it realistically won't happen in the next couple months - if you'd like to start on a Safari version yourself, we'd be happy to provide guidance!

[markmark1]

Thanks for sharing! I’m just requesting the feature not looking to build as I think metamask is missing safari

On Sep 7, 2018 at 12:27 PM,

@markmark1 (https://github.com/markmark1) it realistically won't happen in the next couple months - if you'd like to start on a Safari version yourself, we'd be happy to provide guidance!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/MetaMask/metamask-extension/issues/5173#issuecomment-419541698), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGHomxjht60MFdbptvuNPzhgxIiSGw8Hks5uYsijgaJpZM4WT-u6).

[balupton]

Just wanted to make note that the lack of Safari extension is what is keeping me from MetaMask and all apps that use it. The barrier to entry of installing a less preferred browser, configuring it, opening it, installing some obscure browser extension and configuring that, which I then have to remember to use each time to access some obscure dapp, is too much of an impediment to bother with.

[markmark1]

Thanks for sharing! I agree absolutely

On Dec 5, 2018 at 5:30 PM,

Just wanted to make note that the lack of Safari extension is what is keeping me from MetaMask and all apps that use it. The barrier to entry, of installing a less preferred browser, configuring it, installing some obscure browser extension and configuring that, to access some obscure web app, it too much of an impediment to bother with.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/MetaMask/metamask-extension/issues/5173#issuecomment-444714904), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGHom_u7vYzwOPQDATfjV2kckfS-lrMAks5u2HMggaJpZM4WT-u6).

[mestorlx]

Hi @bdresser how much work you think this could be?
I have some free time now and would love to give back to the open source community. Can you give me some pointers on how to get started so I can see if this is something I can do.

[whymarrh]

Hey folks, as someone who uses Safari as their daily driver, I too would like to see MetaMask on Safari. That said, Safari has a distinct extension model separate from the one that MetaMask uses (basically what @bdresser said above) so this would likely be a medium-to-larger amount of work (to first abstract away the extension model and then to build in Safari support).

It would ideal if Safari came to support the same extension model that every other browser uses, but it is probably technically possible to build support for Safari with its current API. I think efforts are best spent petitioning Apple's Safari team to adopt the standard/join the Browser Extensions Community Group. (Disclaimer: I don't know if Apple is or isn't part of the group, it _seems_ like they aren't. I don't know how the group operates or what level of control they have over the Browser Extensions standards.)

See also: a lot of other extensions talking about their Safari support e.g. RES Safari Support:

It ultimately came down to the direction development of Safari extensions was heading. Major browsers such as Google Chrome, Microsoft Edge and Mozilla Firefox were all adopting a standard commonly known as "WebExtensions". This provides a single API across all browsers. This is hugely beneficial as you can develop for all major browsers from a single code base. Safari is not adopting this standard and instead moving to their own format, with a strong reliance on Xcode. This would require significant investment from the development team to support the browser, as well as core developers having access to Xcode. Supporting this change would mean the codebase for RES would not be unified.

[whymarrh]

I'm going to close this for now. We can re-open this in the future should things change.