You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great Job on everything you've accomplished so far and for open sourcing Xverse.
Now that we onboard so many new people in the Web3 Space and from Bitcoin into Web3, I think it's time to make Web Wallets even more accessible. One step to achieve this would be to make the Extension available for the most used Browser on Macs – Safari.
I think a Safari Extension could give you at least a couple of thousand new users and at the same time make you the no.1 wallet extension on the Apple App Store for Mac.
As a builder myself I would want to onboard my users as easily as possible and not have them switch browser for just one extension, especially because there are a number of reasons why people wouldn't want to switch away from Safari (sync to other Apple devices, keychain, power efficiency, privacy, habits, etc.)
Would love to see that. Keep it up, Xverse!
The text was updated successfully, but these errors were encountered:
Hi Xverse Team,
Great Job on everything you've accomplished so far and for open sourcing Xverse.
Now that we onboard so many new people in the Web3 Space and from Bitcoin into Web3, I think it's time to make Web Wallets even more accessible. One step to achieve this would be to make the Extension available for the most used Browser on Macs – Safari.
I think a Safari Extension could give you at least a couple of thousand new users and at the same time make you the no.1 wallet extension on the Apple App Store for Mac.
As a builder myself I would want to onboard my users as easily as possible and not have them switch browser for just one extension, especially because there are a number of reasons why people wouldn't want to switch away from Safari (sync to other Apple devices, keychain, power efficiency, privacy, habits, etc.)
Would love to see that. Keep it up, Xverse!
The text was updated successfully, but these errors were encountered: