Repository navigation
Updates to Backup & Recovery section - #892
Conversation
✅ Deploy Preview for bitcoin-design-site ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Ready for review on this one. Curious to hear what people think about the How to talk about a recovery phrase section. This content feels out of place to me now that we have expanded the UI flows for every page. Perhaps we should make a graphic that points out in the UI where these sorts of phrases are reflected, as @Bosch-0 suggested? Or perhaps we just strike this altogether and let the text stand for itself within the UI flows? |
GBKS
left a comment
There was a problem hiding this comment.
Looks great. Just had a handful of minor comments.
Regarding the copywriting tips in manual backup, I think it's good to leave it in there. Shows how much care needs to go into these words in this sensitive user flow.
| %} | ||
|
|
||
| {% include picture.html | ||
| image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/recovery/restore-manual-recovery-phrase-progress.png" |
There was a problem hiding this comment.
We should add auto-complete here, as it's enough to enter the first few characters usually.
There was a problem hiding this comment.
Let's discuss this here before I make another commit. My initial thought is that it should be separate and distinct from the OS level autocomplete. The whole advantage is that it should pull from the limited 2048 word BIP39 dictionary.
We can show one screen where we use autocorrection to prevent an error. The below is similar to the existing screen, but we are instead detecting if the word is wrong before the user even finishes typing it. There's no poi words after point in the dict, so the app can assume poil is a typo.
Then we can show an example of where autocomplete prevents the user from having to type in a long word. In this case, hospital, because there are no other hosp words in the dict.
With the above picture, I was thinking about how the user takes advantage of the autocomplete. Do they just tap the word to have it fill automatically? Would they know to do this? What if the autocorrect stood out more? So I made the below image, which would be a little popup that shows the closest guess. The popup is the same color as the primary button, so I think it would stand out as something you interact with.
Another option might be to have a custom autocomplete bar above the keyboard, but that might look kind of tacky in place of the OS autocomplete.
Thoughts?
There was a problem hiding this comment.
I like the OS autocomplete, as long as it only uses words from the word list that is. Also its only required to enter the first 4 letters for each entry, could mention this.
There was a problem hiding this comment.
Stephen and I discussed yesterday. Option 2 seems the way to go, as OS autocompletes don't allow for custom dictionaries. URL bars also have a similar approach to option 2.
There was a problem hiding this comment.
@Bosch-0 I decided against the OS autocomplete. It's doesn't matter to me if feeding the OS autocomplete a custom dictionary is possible or not, because the user may not understand this. Seeing words from their recovery phrase start appearing in the autocomplete might feel somewhat alarming, like the phone is tracking their bitcoin activity or something.
Instead, I added something that I hope feels more familiar to how autocomplete would work in a mobile web browser.
There was a problem hiding this comment.
I like the new design you went for, except for the light blue, doesn't seem to go with everything else.
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
…nto feature/dsw-backup-recovery-2
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
…nto feature/dsw-backup-recovery-2 # Conflicts: # guide/daily-spending-wallet/backup-and-recovery/manual-backup.md
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
…nto feature/dsw-backup-recovery-2
GBKS
left a comment
There was a problem hiding this comment.
Looked through the whole thing again and it looks super good. Just some tiny nitpick stuff I found. Let's get this one out into the world.
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
|
Updated. Ready for another review @GBKS. |
GBKS
left a comment
There was a problem hiding this comment.
tACK. Awesome work, Stephen. Super cool to see this one go live.



Updates to DSW Backup & Recovery. For #763.
💻 Deploy Preview