Hey, thanks for reporting! We're noting this feedback and will take a look how to make this flow better!
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm
I'm checking out Alby Go. Love the simplicity! Except for one thing...
On Receive, I can select "Withdraw" and I need to paste some info but unclear what should go there.
Normally in LN and BTC I expect a BOLT11 invoice, possibly a BOLT12 payment address QR.
The person paying me should then scan that, so that I can receive.
That seems normal UX to me.
Instead, the withdraw option is not well placed or clearly explained within the UX and the flow now becomes me scanning something to receive. I have seen similar inconsistencies in UX before in other wallets, I believe Fountain also had this issue before.
If this points at some more obscure standard-defined way of receiving LN bitcoin, how could we improve the UX? Or should we just drop support for this altogether? What's the benefit of this particular method?
Discussion
Thanks Frens! If you're able to explain what BOLT that button is supposed to support it would be interesting to hear it, pretty sure I encountered the same thing in another app too...
Withdraw supports LNURL-Withdraw :)
Thanks to your feedback I proposed some changes, you can take a look here https://github.com/getAlby/go/issues/280
Very cool, thanks Saunter!
So redeeming sats from somebody already sending them to you (LNURL) vs creating an invoice for people to initiate a new sending operation. This makes more sense!