This repository has been archived!

This IPFS-related repository has been archived, and all issues are therefore frozen. If you want to ask a question or open/continue a discussion related to this repo, please visit the official IPFS forums.

We archive repos for one or more of the following reasons:

• Code or content is unmaintained, and therefore might be broken
• Content is outdated, and therefore may mislead readers
• Code or content evolved into something else and/or has lived on in a different place
• The repository or project is not active in general

Please note that in order to keep the primary IPFS GitHub org tidy, most archived repos are moved into the ipfs-inactive org.

If you feel this repo should not be archived (or portions of it should be moved to a non-archived repo), please reach out and let us know. Archiving can always be reversed if needed.

---

IPFS user research

The IPFS ecosystem of open-source projects has user research and other useful documentation on how people would like to interact with IPFS; where their painpoints are; what is going well for them; what is going less well for them; etc. However, that work is currently spread out across hundreds of repos, websites, and Google docs. This repo hopes to serve as an index for IPFS user research. User research outputs (reports, presentations, etc) will also live here.

Oct/Nov 2019 endevour: pinning ux

A growing challenge for IPFS is to define the product story for how users interact with and think about pins in IPFS. As the number of types of pins increases (for example, pinning selectors), and properties such as ipfs-desktop and soon ipfs-cluster add new entry points for visualizing and managing pins, we need a holistic product story that will unify the communication and visualization of pinsets and their potential interactions in a way users understand.

📌
📌Read about or contribute to this work via issues tagged [Area] Pinning UX.
📌You can also spelunk in this repo's pinning-ux directory.
📌

---

Prior endevours (as of mid-2018)

In 2018, IPFS gathered information and user needs in two areas:

1. What is the simple but complete set of tools, templates, API features and documentation that allows web developers to build distributed applications on top of IPFS and libp2p?
2. How might one store and transfer terabytes or petabytes of data using IPFS?

Research in each area lives in its own directory in this repo, respectively:

1. https://github.com/ipfs/user-research/tree/master/distributed-kit
2. https://github.com/ipfs/user-research/tree/master/large-volumes

Related links

🔒Google drive for not-publicly-accessible documents or unfinished, in-process drafts that are easier to store as Docs/Sheets/etc.

IPFS UX-related links in a list in this repo. PRs welcome if you know of more to add.

Code of Conduct

As part of the IPFS project, this repo follows the IPFS Community Code of Conduct.