Designing BSV products
The design method, and the four places where designing for BSV changes the method rather than just the examples.
How it works covers the technology. This section covers the method: who you are designing for, how to find out, and the frameworks that keep a product honest.
Where to start depends on your role. Designers: start with Common user flows. Researchers: Getting to know your users, then Conducting research. Founders: Personal finance, then Product and business.
Most of the method is ordinary product design. Research is research, personas are personas, and accessibility is not a bitcoin topic. The pages below follow the general method and mark the places where BSV changes it.
Where BSV actually changes the method
Four changes matter most for method. The hard parts covers the full list. Everywhere else, do what you would do for any product.
Mistakes are irreversible. A payment cannot be recalled and a lost key cannot be reset. That raises the stakes on review screens and recovery flows, and it means usability testing has to cover the failure paths as well as the happy one.
Everything is public and permanent. What goes on chain can be read forever, so privacy is decided at design time rather than configured later. See Wallet privacy.
Amounts can be tiny, so new models are possible. Charging per article, per request or per second is practical. There is almost no prior art for it, so the research is yours to do. See Charging per use.
The wallet is a shared surface. Your app asks somebody's wallet for permission. You design one half of a conversation whose other half you do not control. See Connecting a wallet.
The pages
In this section
- Personal finance: the money jobs people have, and which wallet suits each.
- Spending, saving and delegating: three states of mind, one per screen, and the bridges between them.
- Getting to know your users: what motivates people and what stops them.
- Common user flows: the flows nearly every product needs.
- Usage life cycle: from unaware to habitual, and what each stage needs.
- Interoperability: letting people take their money and identity elsewhere.
- Accessibility: where an irreversible payment raises the stakes.
Elsewhere in the guide
- Conducting research: finding out, with the constraints this field adds.
- User personas: five worked examples and their journeys.
- Amounts and units: how to show amounts, which on BSV is mostly in satoshis.
Short on time? Read Amounts and units and Common user flows first. They cover the screens where assumptions brought from elsewhere cost the most.
Related
Written from: BRC-100, BRC-121, BRC-151.