Earlier this year nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x and I implemented ZapPlanner, an app that you can setup scheduled V4V payments. But there are some downsides: 
- They're only standard lightning payments because it can't sign zaps (it doesn't have access to your nostr key) - and I think this is less powerful than zaps because there is no public acknowledgement of your zaps (no-one knows you're contributing except the recipient), and therefore less value returned in the V4V.
- The service is centralized and has to store NWC connection strings to make the payments.

With mobile nostr clients implementing zaps natively this is no longer a problem - proper zaps can be used and the client stores the NWC connection string locally. As long as you open your client every once in a while it can send out any outstanding payments as zaps.

I don't mind that ZapPlanner is now inferior, I am actually happy. We continuously improve and build better solutions for the user and continuously learn. That is how Bitcoin wins.

It might be a bit controversial but I think the same thing with Podcasting 2.0 vs Nostr apps like Zap.stream. As soon as Podcasting 2.0 is properly integrated with Nostr I believe there will be a big boost in payment volume.

$boost #zapscriptions