UX Fix: Importing implicit accounts with zero balance ux
Closed this issue · 7 comments
https://www.loom.com/share/0685ac66114640b1a9df27920ac56168?replyToComment=8707792
Ryan recommends:
recommend clarifying on the center modal that only accounts who have already experienced transactions on-chain will be found, but this secure passphrase is still valid for starting a new account. The "no activity yet" phrase isn't enough, in my opinion. Maybe offer a link from the modal to a page with further explanation.
@nall-near can you take a look at the above request? FYI @Patrick1904
Hi @agileurbanite, I took a look and reworked the copy a bit. Would appreciate yours + @heycorwin feedback. Next step is removing the console error window (top right align).
Just a thought/question: If a user has a valid passphrase, that means they posses the private key for an account. The account either contains funds or it does not, but regardless, they own the account by way of owning its private key. Why not just import the account in any case and not worry about displaying this confusing messaging? The reality is that an account will always be "found" as long as the passphrase is valid. Whether or not that account has been funded or not is a bit of a different matter.
One problem with the language here is primarily with the term "active account". The only other time we use this language in the product is when we are talking about the account that is currently selected by the user in the interface. We don't use the term "active" to describe accounts that have been funded.
Thoughts @nall-near @agileurbanite
Great points @heycorwin. Would also prefer to just avoid the message entirely. It seems like it might be there specifically to address the "hey man, you need to fund/use this thing" agenda.
The main thing I would want to address if required would be the difference between an inaccurate passphrase and account not found on the chain. Curious if the "we can't find your account" comes after some sort of check on chain, and how that differs from going through with the import. I think we need this detail to make the right choice for the messaging.
Need to understand the point of the initial check first, and if we could bypass the "account not found" and go straight to import (would bounce back if the phrase was actually incorrect)
I believe seed phrase validation was something we also had an issue for and were planning on implementing after the implicit account stuff had been completed. @Patrick1904 can confirm.
I believe seed phrase validation was something we also had an issue for and were planning on implementing after the implicit account stuff had been completed. @Patrick1904 can confirm.
The seed phrase validation has been implemented and currently checks whether the provided seed phrase is valid according to bip39-light. The error toast will show if the provided seed phrase is invalid and cannot be used in the near wallet.
The 'import anyway' modal will show if 1. The seed phrase is valid, and 2. The seed phrase/key is not associated with any account
Design Changes
- Remove both the console error and modal warning when user's try to import accounts not found on chain.
- Continue with import if passphrase is valid, importing implicit account
- Display modal window after timeout explaining that their account was imported using attached details
Until a zendesk FAQ is created to clarify "don't recognize this account", we can hide the button and just use the dismiss button.