pull down to refresh

1000 sats \ 1 reply \ @hybridbits 13h \ on: Call for Bitcoin User Interviews bitcoin
Hi there, I'm a UI/UX designer and recently did some independent analysis on Phoenix and LaWallet for a bootcamp.
One of the most common pain points I noticed during the onboarding process for a those Bitcoin wallets is how confusing backup and recovery can be for new users. Many people don't understand what exactly they need to save, how to use it later, or why it matters. For example, mnemonics can be especially confusing. Users often don't know if they're like a password (and if so, what they're used with), or where to input them later (Any wallet? There is something specific they need? etc), and how to store it safely. When wallets provide a JSON file, users frequently don't understand what it is or how they might use it in the future.
Some understand that these things are important, but they don't get how to actually use them to recover a wallet down the line.
Onboarding Observations. Nice-to-haves:
Multi-language support Light mode (helpful for older users and those with visual impairments)
Questions:
Why is wallet inactivity limited to 65535 blocks? Why not allow more? Why doesn't the "Confirm Your Signup" email include "Liana" in the subject line? Adding that could help with recognition.
Cool wallet btw!
write
preview
0 sats \ 0 replies \ @Wizardsardine OP 13h
Thanks for the great feedback! Your observations about confusion during the backup/recovery process really resonate!
The 65535 block limit on timelocks is a Bitcoin consensus thing. It may change in the future, but currently, relative timelocks cannot be longer.
The signup confirmation email for using our node should definitely include "Liana" - great point!
reply