I agree with this!

However:
*it may still be good to send a message in the dms
*the improvement mentioned in the claim screen, I agree is a prerequisite for automatic sending; but maybe not if given as a choice 

 cc +npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226 I just tested the withdrawal flow here, Instead of having the user manually submit the invoice you could use webln.makeInvoice(). Saves the user from manually having to generate an address if WebLN is available... 

 „Withdraw to Alby“ 💪⚡️ 

 I think it should just auto-withdraw once a user sets a lightning address in their profile.  

 Side note: why don't we have multiple payment options in the profile, so that we could use stuff as fallback? 🤔 

 CC @starbuilder 

 That’s a pretty neat idea, but also an edge case. The idea is to provide an address in the first place. 

 Onboarding new users that know nothing is not an edge case.  

 But isn’t this the opposite of what you said above? New users can have a seamless experience with npub.cash, by setting their Lightning address to their npub.cash address. Clients could display the balance within their UI, no friction whatsoever 

 I'm tired. I'll explain next week. Sorry.  

 Yeah, but then your idea is less exciting. If you already have a wallet address in your profile, then we could make it work. 

But I thought the goal was to make it work for people without any address in their profile. They woundn't have a place to auto-withdraw.  

 I mean auto-withdraw from the npub.cash side.  

 Strongly agree! The webpage was meant as a POC. The idea is that apps and wallets implement the API directly. Amethyst users could use their npub.cash address absolutely seamlessly.

We are currently strengthening foundations, adding proper CI and testing etc. Once that’s done we will revisit the webpage, even though it would be best if apps implement it directly