Anzus · I work in BD and support at Gem Wallet, rather than as a developer. One recurring usability issue I notice is that beginners often see on-chain Bitcoin and Lightning simply as “BTC,” without understanding that the payment and recovery experience may differ.
This creates several moments where a wallet has to decide how much information to show.
Receiving
Should users choose between on-chain and Lightning before seeing payment details, or should the wallet guide them based on what they are trying to do? How much explanation is necessary without overwhelming someone making their first payment?
Sending
When a user pastes an address or invoice, the wallet can often identify the payment type automatically. Should the confirmation screen still label it clearly as on-chain or Lightning and explain the expected fee, speed and possible failure conditions?
Backup and recovery
“Your seed phrase backs up your wallet” sounds simple, but what it restores can depend on the wallet’s Lightning design. How should a wallet explain this accurately before a device is lost, without presenting users with implementation details they may not understand?
Payment failures
Should the difference between the two systems remain mostly hidden until something goes wrong, or does hiding it create an inaccurate expectation that all Bitcoin payments behave the same way?
There seems to be a tradeoff between showing too much information and giving users an overly simplified mental model. I’m interested in how wallet developers approach this boundary.
Are there interface patterns, terminology or user-testing results that have worked particularly well? At what point—onboarding, receiving, confirmation or backup—should these differences be explained?