Add support for non-Chrome browsers

[john-light]

The app currently has an error when the user visits in a non-Chrome browser:

Only Chrome browser is allowed

It would be great if the app could be used in non-Chrome browsers (e.g. Firefox-based browsers) too.

[josedahlquist]

We've found some issues with the hardware wallets that made us decide to focus for the initial release on Chrome alone.
We will work on expanding the compatibility for the next release.
Thanks for bringing this up

[raucao]

It shouldn't be a problem with Trezor, because it's using the Trezor Bridge anyway. In any case, I don't understand the need for requiring specific wallets for the app in the first place. Can't it just show a BTC address to send to from any wallet?

Ledger and Trezor may have large market shares, but they're obviously by far not the only wallets that people use. Requiring people to use an abysmally slow NFT wallet like Liquality to pipe their BTC through on the way to RBTC generally seems like a non-optimal design to me.

I would propose a 4th connect option, which would be to enter either a list of addresses, or simply an XPUB to use, so that the app becomes compatible with all other wallets in the ecosystem.

[alexjavabraz]

@raucao appreciate your comment, currently, we're testing every version to maintain compatibility with some hardware wallets. What guides us to new implementations and improvements are the needs and suggestions of our customers, so we welcome your suggestions and we will evaluate the possibility of making it as flexible as possible.

[john-light]

@raucao your comment is off-topic to this issue, so I created a new issue to discuss here

[raucao]

Appreciate it. However, it's not entirely OT, because:

We've found some issues with the hardware wallets that made us decide to focus for the initial release on Chrome alone.

So adding support for all bitcoin wallets would also add support for all browsers.