Add more info for wallets on wallet kit

[janewang]

Problem

The term “Not Available” is overloaded in the current wallet UI. It’s being used to mean:

• The wallet is not installed.
• The wallet exists, but cannot be used on the current platform (e.g. a mobile-only wallet when on desktop).

This creates confusion for users. For example, if I visit with Hana Wallet and only see “Not Available,” I don’t understand whether it’s because I need to install it, or because my platform isn’t supported.

Proposal

Decouple states into two callouts:

• Install → visible as a link out to the wallet’s installation page/store.
• Not Available → used only when the wallet is unsupported on the user’s current platform.

Platform awareness:

Show the Install link only if the user is on a platform where installation is possible (e.g., Chrome desktop → show Chrome extension install link).
For unsupported platforms (e.g., desktop browser for a mobile-only wallet), show Not Available.

Additional clarity:

Consider adding a small platform tag (e.g., Desktop, Mobile, Extension) next to each wallet, so users can quickly understand compatibility.

[JakeUrban]

Wouldn't it be better to just hide wallets that aren't available on the user's platform, rather than having "Not Available"?

[earrietadev]

@janewang I agree with @JakeUrban in not showing the wallet if we know is unsupported by the platform, I also believe is going to be difficult to know that a wallet is supported or not in all cases, for example a Ledger device is supported on mobile based on the browser and version of the OS you are using, but we can make it so if the kit is not fully sure it just shows the install button instead of hiding it. That way we avoid hiding wallets because of false positives

[devodii]

hey @earrietadev, any updates on this?
i have v2.0.1 from jsr and i still see the "install" button when the auth modal is opened on an android device. shouldn't be as chrome extensions can't be installed on androids, same for iOS.

[earrietadev]

Hi @devodii, this hasn't been implemented yet because because we need to think of the edge cases first. For example you mentioned that chrome extensions can not be installed on Android but that's wrong because android user who use browsers like Kiwi or any other chromium based browser with the feature enabled can indeed install chrome extensions, same if they are using Firefox so being on Android alone is not enough to determine if we should hide or not an option. For iOS it could be a little easier at least for now.

[devodii]

thanks for the response @earrietadev, please let me know how that goes. btw i was the person that reached out on x yesterday asking to see how the walletkit is being implemented at blend capital. wallet connect works so well there especially how it links my lobstr wallet. but when i try setting it up on my project i get this error when users want to link their lobstr wallet.

this is the ui after clicking on walletconnect option from the wallet options from my app

which is very different from the display after choosing walletconnect on blend capital mainnet

do you have any ideas on how this can be fixed? 🙏🏽