Replies: 2 comments 2 replies
-
The concept of an XPUB and the different xpub types are not something we have invented. Similar UIs exist in other apps that import xpubs. Embedding those hints in the UI may work as an improvement but autodetection is tricky as those prefixes are just hints and not everyone follows them. Using an XPUB is not easy so the user needs some kind of expertise. |
Beta Was this translation helpful? Give feedback.
-
Sure, of course :)
Actually my feedback is coming from my experience that some of your rivals make this far friendlier to users. For instance, Coinstats doesn't mention a single technical term, just asks the user to paste:
They will, trust me :)
Autodetection could include a check whether any balances were found. If no balance was found, let the user know that something went wrong and that they'll need to provide more info about the key type. And then guide them through how to find out and provide that info. Even a deeplink to the relevant docs would be an enormous improvement!
I'd challenge that way of thinking. If users need this kind of expertise then we won't onboard the next [mbtz]illion users into crypto, or at least not into rotki. Waiting for users to learn about P2PKH vs. P2TR etc. is unfortunately doomed to fail. In contrast, a great UI can guide a user into gaining the relevant expertise, rather than just implying "go away and learn stuff, and come back when you're ready". |
Beta Was this translation helpful? Give feedback.
-
|
I just rediscovered #1664 which was basically about me struggling with exactly the same thing in 2020. Originally reported on Discord: https://discord.com/channels/657906918408585217/745172610240872508/771720464463822870 |
Beta Was this translation helpful? Give feedback.
-
|
After much trial and error, I found I could import the xpub by using https://jlopp.github.io/xpub-converter/ to convert to zpub and then pasting the zpub in the xpub field. ypub didn't work, however! I think this is further evidence that the process needs significant simplification. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say I'm a newbie user adding a Bitcoin account to Rotki. The first choice in the dialog is "Manual" or "XPUB". That's already pretty cryptic for a newbie, so I think there needs to be a quick explanation of how to choose the right one.
That aside, let's say I now choose "XPUB". Now I see this:
In the first field, I'm expected to choose between P2PKH, P2SH-P2WPKH, WPKH, and P2TR. Honestly this would be enough for a lot of users to run away screaming! I'm technical, with some understanding of terms like "segwit", "native segwit", "taproot", and yet even these slightly more human-readable terms are not mentioned. This seems like a very strange approach to UX, almost as if the app is built primarily for cryptographers and experts, but surely that's not the intention?
Better would be to embed the helpful hints already in the documentation:
But best of all would be to say "just paste your key in here", do as much auto-detection as possible, and if it's not possible, then display a message guiding the user on how to provide the needed information.
Just in case there's any doubt, while it's awesome that Rotki has thorough docs, this is not a substitute for good UI. There's a "Don't Make Me Think" design principle which means that if your user has to read the docs to understand the UI, your UI design has failed.
Beta Was this translation helpful? Give feedback.
All reactions