Nostr Web Client

If you're spending micro-sums all the time on zaps and products/services, you need a reference point for all that spending. Same with earning.

Budgeting apps is exactly the sort of apps to take inspiration from. But it needs to be integrated.

Matt 1y ago

I guess we agree then. I just think it would make more sense to connect two different pieces of software to avoid redundancy and increased attack surface. I'm imagining Bitcoin budget apps that can connect to Wallet apps without necessarily having an integrated codebase. And it avoids added complexity for those who don't want it. Similar to how budget apps now connect to bank accounts.

I'm realizing now that there's a fundamental difference in how some of us use "wallets." I keep larger Bitcoin stacks (like bank savings accounts) and move funds into hot mobile wallets for spending, much like I would with cash. So for me it wouldn't make sense to have my budget app built into a hot wallet, since it isn't my primary "account." It merely facilitates spends and receives for me. I'd want a separate budget app that can connect many other apps for a broader use case.

Either way, you can simulate what you want while getting the benefits of separate functionality. There's no reason we can't have both, I'm just thinking about modularity and security alongside UX.

Reply to this note

Please Login to reply.

Discussion

Matt 1y ago

When I say security I'm referring to attack surface (more code and features) and separation of duties principles. Something that deals with money should have the smallest possible attack surface in my opinion, which in this case means the smallest possible codebase. Added functionality can come from other, connected software if some users want. It's a best of both worlds approach where people can decide how they want to use software rather than just packing everything into one app regardless of whether people want it or not. Similar to how addons and plugins work.

Niel Liesmons 1y ago

If this wallet is a #Cashu wallet that lives on your relay(s).

Then it's already a widget that you plug-in/access from within this main app.

Once you give permission (via signer or nsec) to access it's data and to send and receive small payments, you might as well stay in the same app, right?

And if the budget and earning goal is part of the wallet event kind, that's even more true.

Big payments or whatever other dangerous actions can still require permission form a limited-code-base signer app in this scenario.

I'm not advocating for people to hold savings in these wallets neither, hence the need for things like budgets to build features like auto-send-to-savings on.