Week 3: Keys, Wallet Creation, Backup

Challenge: Crafting User Flows

This week, you’ll try to balance the human experience with the technical reality. Wireframes or low-fidelity mockups are OK, most important is that you show an understanding of the problem space and have come up with an intuitive, human-centered solution. Try adding a unique creative element.

Step 1: Choose One of the Challenges

• Backup status: Design a way to show users the current state of their wallet backup. Consider multiple backup types and clear status communication.
• Recovery phrase verification: Design a process for verifying that a user has correctly written down their recovery phrase. Focus on error prevention, clarity of instructions, and accessibility. The goal is 100% accuracy.
• Watch-only wallet setup: Design the process of importing just a public key to create a watch-only wallet. Help users understand what they can and cannot do without the private key.
• Key backup scheduling: Design a simple system that helps users regularly verify their private key backups are accessible. Make it a clear, repeatable process.
• Post-backup testing: Design specific verification challenges that confirm users can actually use their backed-up private keys to recover funds. Focus on confidence building.
• Old key archival: Design an interface for safely archiving old private keys that might still control some funds. Consider future access needs and security requirements.
• First key generation: Design the exact moment a user generates their first private key. Show what's happening, explain the implications, and help them feel confident. Consider showing a metaphor or visualization that helps them grasp the concept.
• Message signing: Design an interface for someone signing their first Bitcoin message. The goal is helping them understand what signing proves, what it doesn't prove, and common use cases (like proving ownership of an address). Consider what questions they'll have, their mental model of "signing," and how to build confidence in this cryptographic action.

Step 2: Define the User Flow

• Outline how a user would go through this process in your design.
• Identify key decisions or challenges they might face.

Step 3: Create Wireframes or Low-Fidelity Mockups

• Sketch out the core screens or interactions.
• Keep it simple — focus on making the experience intuitive.

Step 4: Add a Unique Creative Element

• Think beyond standard solutions.
• How can you make this more engaging, reassuring, or seamless for users?

Step 5: Document Your Thought Process

• Briefly explain your design decisions and trade-offs.
• Highlight how your solution balances security and usability.

Submitting Your Work

Deliverables:

Your design documentation should include:

• User flow diagrams (Show how a user moves through your design)
• Wireframes or low-fidelity mockups (Showcase key screens or interactions)
• Text summary (Explain your approach, decisions, and how your solution balances security and usability)
• (Optional) Video documentation (A short walkthrough (e.g., Loom) sharing your thought process)
• (Optional) Interactive prototype (If relevant, demonstrate key interactions)

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

Evaluation Criteria

• Does the design clearly communicate security risks and tradeoffs?
• Is the design approachable for new and experienced users?
• How well does the diagram prevent the user from making mistakes?
• How clearly did you document your design process and solution?

Useful Resources

Bitcoin UI Kit
Bitcoin Icons