Week 4: Wallet Design Patterns

Challenge: Crafting User Flows

This week, you’ll focus on refining wallet interactions to make Bitcoin more intuitive and user-friendly. Choose one of the challenges below and design an interface that balances human experience with technical constraints. High-fidelity mockups are key here — your design should be polished, functional, and human-centered.

Step 1: Choose One of the Challenges

• First lightning payment: Design a single screen that helps a user confirm their first-ever lightning payment went through successfully. Include what happened, why it succeeded, and what they can do next. Consider their emotional state and need for reassurance.
• Viewing sensitive data: Design the interaction for temporarily revealing/hiding a wallet balance in public. Consider speed of access, privacy, and accidental reveals. Think through edge cases like accessibility settings.
• Payment failure explanation: Design an error message system that explains why a lightning payment failed and what to do next. Focus on clarity and actionable next steps without technical jargon.
• Fee selection: Design an interface for choosing mining fees that helps users understand the tradeoff between cost and confirmation time. Use real numbers and scenarios.
• Contact management: Design an interface for managing saved payment destinations (addresses, lightning, contact info). Focus on organization and quick access.
• Transaction labeling: Design an interface for adding notes and categories to transactions. Consider bulk actions and search/filter needs.
• Spend limit setup: Design an interface for parents to set spending limits on a teenager's wallet. Focus on flexibility and clarity of restrictions.
• Address reuse warning: Design a warning that helps users understand why reusing addresses is bad for privacy. Focus on education without fear.
• First receive request: Design an interface for helping a user receive their first Bitcoin payment. Consider explaining addresses vs lightning invoices, QR code sharing options, and expected wait times. Focus on building confidence and reducing anxiety about "doing it wrong."
• Multiple account switching: Design a system for users to quickly switch between different wallet accounts (e.g., savings, spending, business). Consider visual differentiation, account naming, and prevention of accidental sends from wrong accounts.
• Payment proof saving: Design a system for saving and organizing payment proofs (transaction IDs, lightning payment preimages). Consider different sharing needs and privacy implications.

Step 2: Understand the Problem

• Consider real user needs, potential friction points.
• Work out how best to communicate key information

Step 3: Design

• Create high-fidelity mockups that demonstrate the interaction.

Step 4: Document Your Process

• Provide a short written explanation of your approach, design choices, and how your solution improves usability.

Step 5: Consider Edge Cases

• Think about accessibility, potential errors, and different user scenarios.

Submitting Your Work

Deliverables:

A complete design package including:

• High-fidelity designs showing key screens, states and interactions
• Short written explanation of your design process and decisions

Whiteboard tools or documents work well for this challenge. Focus on clarity over polish.

Evaluation Criteria

• Is the interface visually cohesive and intuitive?
• Can this design be used by a broad audience?
• How clear is it to users what the main action is on each screen?
• Does the design effectively present the intended functionality?
• Are Bitcoin design principles appropriately implemented?

Focus on doing one thing really well instead of trying to solve everything at once. Keep technical constraints in mind and consider important edge cases.