BitcoinDesign
📱 Revise `Daily spending wallet` -> `Privacy` page
This issue will be part of a bigger milestone that focuses on revising the newly formed Daily spending wallet reference design we now have in the guide.
The current privacy page in Daily spending wallet is more of a general overview of wallet privacy and isn't specific to a daily spending wallet. We should make the content of the page specific to daily spending wallets and add some UI designs illustrating the concepts.
Some of the more general content may be more suited for a Privacy page in the How it works section which covers the technology / general considerations outside of specific contexts like a daily spending wallet. Though this is an issue for another time.
Page: https://bitcoin.design/guide/daily-spending-wallet/privacy/
Need to add new content around:
- NFC privacy considerations https://github.com/BitcoinDesign/Guide/issues/580
- Hiding home screen balances: https://github.com/BitcoinDesign/Guide/issues/578
Relevant info for tackling this page:
- https://www.youtube.com/watch?v=Cjxc9ERz2mU
- https://abytesjourney.com/lightning-privacy/
- https://en.bitcoin.it/wiki/Privacy
- https://voltage.cloud/blog/bitcoin-education/how-taproot-improves-the-lightning-network/
Also want to look into LSPs and lightning wallet servers and the privacy trade-offs with using them in your applications.
- https://www.youtube.com/watch?v=jXjsxvuxByc
- https://bitcoin.design/guide/how-it-works/lightning-service-providers/
For these revision pages the images should also be generally updated:
- Ensure they reflect what is shown in the UI kit
- Apply new modal formatting to images
- Remove grey area on the iPhone 'dip' at the top of the phone (see below).
As noted here, we should move the "Privacy checklist" and "Hiding sensitive information" part of the Security page to this page. This will add more UX guidance to this page that is otherwise more focused on techniques. For those, we should also consider how we can make them more practical (-> mockups).
I can take on this page. As we discussed in a recent jam session, some of the more under-the-hood content from this page is better suited for "How it works". Instead, we can include more mock-ups that show where privacy considerations surface in the UI (like a receive screen showing a new address every time). Designers should understand some of the basics, like that on-chain transactions are public and preserved forever and lightning transactions aren't. So we'll have to explain a few things for sure, but maybe not go all the way down to inputs and outputs here. I'll start this with a draft in a Google Doc.