I find creatr to be too hard to use. Iām sure itās easy if youāre the kind of person who uses bitcoin and lightening outside of Nostr, but for normies this is hard. If i could pay for it FROM a nostr app, with a zap, then itād be easier. But as it is, itās like go use x software, then y software, then copy this code (relay address) and put it in the right spot. As a proof of concept, i like it, and iām excited about being able to pay for subscription content on nostr, but this needs some user testing.
Repost my stuff! I could use some subscribers on my nostr:npub1creatr06r4vr7rzx22f4kawdfj82yt09vw5rqw0kan8sr43h608s3dfeh6 haha
Discussion
nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz check out this user review!
Is it possible that people could get a DM and zap it and things would work?
We could certainly DM an invoice - thatās easy to do. How should a user signal they want an invoice from within their nostr client?
We could make it a chat bot with commands like nostr:npub1fyvwkve2gxm3h2d8fvwuvsnkell4jtj4zpae8w4w8zhn2g89t96s0tsfuk but that seemed a bit archaic to me.
Maybe there could be some kind of āsubscribe nowā button on the paywall splash? Or maybe the link that takes them to the website currently instead just says subscribe now and if you click it a dm is sent? Or even better would be that link just auto generates an invoice for that npub and sends them to a wallet for payment?
I agree that itās not ready for prime time. Thatās why I primarily use it in a way where there are public images followed by subscription imagery. This way people can still see some of my work and zap me the normal nostr way.
Also, instead of posting less public stuff, Iām trying to simply post MORE content, keeping my typical 2-3 image posts public but adding an additional 2-3 images to the post as well.
I think I might stop āpromotingā the creatr aspect all together, as I think it lowers the signal of the art by having āadvertisingā type language in the post, but I also want to help Mazin spread the wordā¦ so thatās a tough one.
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?