We don’t just chat about design. We also actively improve design in the bitcoin ecosystem. Projects launched by community members often focus on creating design resources.
With collaborations, some of us try to help other bitcoin projects improve their products’ design and user experience. For more details, see our Collaboration and Project documents. If you are interested in getting involved, reach out directly to the projects below, or reach out in our Slack.
These are some of the design projects we have initiated ourselves.
The primary project we are working on, a resource for designers to create better bitcoin products faster.
Icons for typical needs of bitcoin applications. Includes common generic icons like arrows, and more unique ones like a wallet, keys, mining, and bitcoin symbols.
A complete design system to serve as a foundation for wallet concepts, prototypes and application development.
Improving lightning network wallets through applying the design guide, design thinking and problem solving.
Help get unified QR codes adopted for smoother payment flows.
We organized a hackathon for designers.
For a more complete list of current and past collaborations, see our collaboration board.
Alby brings Bitcoin to the web with in-browser payments and identity, no account required.
Building an application that lets users easily run full bitcoin nodes.
Raising bitcoin for dentistry treatments.
Hello Bitcoin is a volunteer-run project with the simple goal of helping people learn about bitcoin in a way that is friendly and accessible.
Building a web UI for JoinMarket which is software used to create private bitcoin transactions called CoinJoins.
Zeus is an open-source, non-custodial bitcoin wallet that gives you full control over how you make payments.
Learn about the lightning network, post your apps on the market, and join our hackathons.
Adding a project or collaboration
The Bitcoin Design Community is intentionally only loosely organized. This makes it difficult to define specific rules of what is a community effort and what isn’t. Best approach is to get consensus by asking in the #general channel in Slack or opening an issue in the meta repo on Github.