Open-source wallets are often recommended because their code can be inspected publicly, but how important is that to you when choosing an Algorand wallet?
What benefits do you value most—transparency, independent review, community contributions, or visibility into how keys and transactions are handled? What limitations or misconceptions should users understand?
I’m asking partly to understand what users expect from open-source wallets such as Gem Wallet, which supports Algorand. Both user and developer perspectives are welcome.
Being able to connect to dApps is part of supporting Algorand. Otherwise the wallet is limited to transactions that are composed in-wallet (no app calls, etc). Take a look at use-wallet, an Algorand wallet integration library.
That’s a fair point. Gem Wallet does not currently support dApp connections on Algorand, so this is a limitation.
Looking at use-wallet, I see it supports both dedicated wallet adapters and a WalletConnect adapter. From a dApp developer’s perspective, would compatibility through WalletConnect be sufficient, or would a dedicated Gem Wallet adapter be preferable?
This is exactly the kind of practical feedback I was hoping to gather. Thanks for raising it.