Skip to content

UX_MASS_ADOPTION.md

Latest commit

 

History

History
271 lines (201 loc) · 8.21 KB

UX_MASS_ADOPTION.md

File metadata and controls

271 lines (201 loc) · 8.21 KB

RuneBolt UX & Mass Adoption Strategy

Transforming RuneBolt from a developer tool into a consumer-ready product

Executive Summary

RuneBolt is positioned as "Lightning Network for Runes" — a hub-based channel system for instant DOG transfers. This document provides a comprehensive UX transformation strategy.

1. The Mass Adoption Problem

Why Lightning Network Hasn't Gone Mainstream

Barrier Technical Reality User Experience
Channel Management Users must open/close channels "What is a channel?"
Inbound Liquidity Need incoming capacity "Why can't I receive money?"
Path Finding Complex routing "Payment failed - no route found"
Recovery Channel state backups Lost funds due to backup failures
Terminology Satoshis, HTLCs "I just want to send money"

What Successful Apps Get Right

Phantom Wallet (15M+ MAU):

  • 4-step signup process (< 1 minute)
  • Human-readable usernames instead of addresses
  • Social login options alongside seed phrase
  • Clean, minimalistic design

Cash App (50M+ users):

  • Bold, personality-driven UI
  • "You don't need onboarding videos, just a thumb and curiosity"
  • Actions streamlined while personality retained

Venmo (80M+ users):

  • Social feed makes payments feel natural
  • Username search (not account numbers)
  • Payment memos humanize transactions

2. The RuneBolt UX Transformation

Mental Model Shift

Current (Developer-Focused):

User → Opens Channel → Manages Liquidity → Sends → Closes Channel

Target (Consumer-Focused):

User → Deposits DOG → Sends to Anyone Instantly → Done

Core UX Principles

  1. Hide the Channel — Implementation detail, not user-facing
  2. Human Names — @username instead of pubkeys
  3. Instant Feedback — Every action has immediate visual confirmation
  4. No Crypto Jargon — Everyday language only
  5. Mobile-First — Design for thumbs
  6. Progressive Disclosure — Simple by default, powerful when needed

3. Onboarding Flow Redesign

Proposed State

Landing → Create Account → Add DOG → Start Sending

Goal: 3 steps, under 90 seconds to first transaction

Onboarding Checklist

Requirement Priority Implementation
Sub-90 second path to first transaction P0 Remove all optional steps
Social login (Google/Apple/Email) P0 Privy or Magic Link
Bitcoin wallet connect P0 Unisat, Xverse, Leather
Username-based addressing P0 RuneBolt DNS
Buy DOG with card P1 MoonPay/Transak
Skip deposit option P1 Allow exploration

4. User-Friendly Error Messages

Principles

  1. Explain in plain English
  2. Provide next steps
  3. Use friendly tone
  4. Visual clarity (icon + heading + explanation + action)

Error Message Library

Scenario Before After
Wallet not connected "No wallet provider detected" "Connect your wallet to continue"
Insufficient funds "Insufficient DOG balance" "You need 1,500 more DOG. Add funds or reduce the amount."
Channel not open "No active channel found" "Your account needs DOG to send. Add at least 1,000 DOG to get started."
Recipient not found "Recipient pubkey not found" "We couldn't find @username. Check the spelling or ask them to join RuneBolt."

5. Transaction Status Visibility

Three-State Model

State Visual User Message
Sending Animated spinner "Sending to @mike..."
Sent Green checkmark "Sent! @mike received 1,000 DOG"
Received Confetti animation "You received 1,000 DOG from @sarah!"

6. Trust-Building UI Elements

Security Badges

Badge Placement Purpose
🔒 Non-Custodial Footer, settings Reassures users they control funds
✅ Open Source About page Transparency builds trust
🛡️ Audited Security page Third-party validation
⚡ Instant Send/receive screens Highlights key benefit

Trust Signals to Implement

  1. Balance Visibility

    • Show DOG balance prominently
    • Show USD equivalent (toggleable)
    • "Your DOG, your control" microcopy

  2. Transaction Confirmations

    • "Sent instantly via RuneBolt" on success
    • "Secured by Bitcoin" in footer
    • "Non-custodial: only you control your keys"

  3. Educational Tooltips

    • "What is RuneBolt?" explainer
    • "How is this instant?" (brief channel explanation)
    • "Is my DOG safe?" security overview

7. Mobile-First Design

Key Mobile UX Principles

  1. Thumb Zones

    • Primary actions in bottom 25% of screen
    • Balance and key info in top 50%
    • Navigation reachable with one hand

  2. Touch Targets

    • Minimum 44px touch targets
    • Generous spacing between buttons
    • Swipe gestures for common actions

  3. Quick Actions

    • Send/Receive as primary FABs
    • Recent contacts on home screen
    • Pull-to-refresh for balance

8. Social Features

Contacts System

┌─────────────────────────────────────┐
│   Send DOG                          │
│                                     │
│   [Search @username or name    ]    │
│                                     │
│   Recent                            │
│   ┌────┐ ┌────┐ ┌────┐             │
│   │ 🧔 │ │ 👩 │ │ 🐶 │             │
│   │Mike│ │Amy │ │DOG │             │
│   └────┘ └────┘ └────┘             │
│                                     │
│   Suggestions                       │
│   [+] Import from Contacts          │
│                                     │
└─────────────────────────────────────┘

Transaction Memos

  • Emoji support in memos
  • Preset memo templates ("🍕 Lunch", "🏠 Rent", "💝 Gift")
  • Private memos (only sender/receiver see)

Shareable Links

Link Type Format Use Case
Profile runebolt.io/username Share to receive
Payment Request runebolt.io/pay/username?amount=1000 Request specific amount
Claim Link runebolt.io/claim/abc123 Send to non-users

9. Implementation Roadmap

Phase 1: Foundation (Weeks 1-4)

  • Implement social login (Privy/Magic)
  • Build username system
  • Redesign onboarding flow
  • Rewrite all error messages

Phase 2: Polish (Weeks 5-8)

  • Mobile UI overhaul
  • Transaction status redesign
  • Add trust badges and education
  • Implement contacts system

Phase 3: Growth (Weeks 9-12)

  • Shareable payment links
  • Claim links for non-users
  • Referral program
  • Merchant tools

10. Success Metrics

Metric Current Target Measurement
Time to first transaction ~5 min <90 sec Analytics funnel
Onboarding completion Unknown >70% Signup analytics
User error rate Unknown <5% Error tracking
Support tickets Unknown -50% Support system
NPS score Unknown >50 In-app survey
DAU/MAU ratio Unknown >30% Engagement tracking

Research Summary

Why Phantom Succeeded

  1. Started with Solana (fast, cheap) — reduced complexity
  2. Social login reduced friction for new users
  3. Human-readable names eliminated address anxiety
  4. Clean UI hid blockchain complexity
  5. Built for non-technical users first

Why Lightning Struggles

  1. Channel management is too technical for average users
  2. Inbound liquidity confusion
  3. "No route found" errors with no clear resolution
  4. Recovery is scary and complex
  5. Terminology barrier (satoshis, nodes, invoices)

What Cash App Proves

  1. Personality + simplicity wins Gen Z
  2. You don't need to explain how it works
  3. Bold, confident design reduces anxiety
  4. Actions should be faster than explanations

Document created: March 14, 2026 Approach: User research → Hypothesis → Prototype → Test → Iterate