GBKS on Nostr: nostr:note1mgymdhtc0qk7nxjn7nqduhe637lytal2hq8m0jgl4qp8rzus8sas52lq40 This page was ...

quoting note1mgy…lq40

If you're designing a bitcoin application that can manage multiple wallets in parallel, there's a new reference design in the guide that might interest you. It starts with use cases and key handling and dives into diverse user flows.

https://bitcoin.design/guide/multiple-wallets/

It's a quite intricate design. In the review process, the team spent 2 hours reading through the page together. If you'd like to learn by listening to these conversations, here are the recordings.

https://www.youtube.com/watch?v=r0K-UG-ozb4
https://www.youtube.com/watch?v=Y4ozpWl_aQc

This is the first iteration of this page and we'd love to hear your feedback to improve it. Thank you to all who contributed to this page already.

This page was really intricate to work on. Trickiest part was finding the right balance of keeping wallets separate vs combining them, especially when it comes to keys. What simplified this was starting with a clear use case.

Clear use cases are essential for making design decisions throughout the user experience. Without them, you're often deciding by personal preference, group dynamics, etc. You might be OK if you build a general purpose tool.

Money is handled and managed in endless different ways around the globe. But I think we can establish some frameworks to help us find categories of behavior and then design products for them. I like this page as a starting point. https://bitcoin.design/guide/designing-products/personal-finance/