Design Deep Dive on IPFS apps
IPFS Camp · IPFS Camp · 2019 · 2 min
What an IPFS app needs before normal people can use it: hide the hashes, the peers, and the pinning behind a real product.
A talk at IPFS Camp, the Protocol Labs gathering for the people building IPFS, on the design patterns a decentralized app actually needs to feel usable12.
The primitives were powerful and unfamiliar: content addressing, peer-to-peer distribution, user-held identity. The recurring failure was making the user carry that unfamiliarity. I walked through the patterns for hiding the stack12, so a person experiences a normal app and never has to think about how it is stored or addressed underneath.
It is the same thread as the rest of my open-web work312: the technology can be new, but the experience has to feel familiar.
Sources
- Design Patterns for the DWeb
- Publishing on the Decentralized Web
- DNS and Marigold on social rollups (archived)