BDG article about challenges building with Lightning #21
Description
Following the call (notes) about UX challenges building with lightning, add an article with a list of problems and solutions to common issues:
- Running a node on a mobile device --> LDKnode
- How to back up state of lightning node/channels (on top of backing up recovery phrase)
- How much data? (10kb - 1mb)
- Mutiny - Encrypted file stored on their servers
- Versioned Storage Service
- Unit representation (bitcoin vs sats vs fiat)
- How to communicate fees? (channel costs, lsp costs etc)
More notes
How to communicate lightning to users? How can icons and graphics help?
Surprising for existing crypto users
Weird to type an amount to create an invoice
Different starting point than complete newcomers
Phoenix mentioned as a good example for how to communicate
Backing up state is a unique lightning challenge
Mutiny - Encrypted file stored on their servers
Versioned Storage Service
Nayuta
English, Spanish, Japanese
Japanese is longer, harder to explain
Unit formatting across countries
Informing users intelligently about fee spikes
Hitomi shared an anecdote about a friend being confused about the lightning symbol, not sure what it meant. Another thing to understand in addition to bitcoin.
Tension around trying to force a Venmo/Cashapp style UI. Are we well-served by that or embrace bitcoin-specific properties a bit more?
Typical issues
Running a node on the device is hard (are remote nodes a la Greenlight a solution?)
LSPs need to lock up channel liquidity (biz model?)
0-conf channel for instant liquidity (but secure?)
Fees for channel opens and rebalances
Online requirement for receiving payments?
Need to get an invoice in order to pay someone
Non custodial on Lightning
Backups
Encrypted cloud back up done automatically (Daniel)
Privacy
Payment routing or block fetching
Liquidity:
How do I receive bitcoin without needing to know anything about channels?
Explaining liquidity to users? How to?
State of node or channels