Thanks Rabble, appreciate you taking the time.

I agree, of course, that there’s too much friction and switching for now. Unfortunately, I think without building our own client (which we strictly want to avoid) there are going to be UX tradeoffs. 

My perception is zaps aren’t useful for subscriptions. What do they zap? How do they know how much to zap? What happens if a user underpays for a subscription by 1 sat? How about overpays (perhaps even exceeding the max subscription duration limit)? What about if they zap the wrong note or person? Who will track and address these customer support issues? 

Invoices just work and make sense and NWC makes this process smooth. After your first payment we show a “Connect Wallet” button to send future invoices. If we could get the users wallet connected up front, all they would need to do is signal they wanted to subscribe to a certain user and we would automatically send them a pay req via NWC. Maybe that’s the best route?