Background

Pioneer is explained here.

Problem

The number of UX problems in Pioneer is overwhelming. Users enter the experience either to learn about Joystream for the first time, via the website, or are coming to do certain tasks on our testnets, but its all very noisy and difficult. At the same time, we have to be cautious about how much effort we invest in improving these problems, as Pioneer itself will be redesigned from scratch in the near future.

Goal

Attempt to make opportunistic small improvements to the UX of Pioneer which are easy to implement and deploy, yet have a substantial payoff to the effectiveness of the product.

Proposal

1. Review the current state of Pioneer, and pay particular attention to what users have to do by reading the documentation and communication published on the current (Rome/Constantinople) testnet.

2. Compile a list of UX problems. Importantly, these have to be problems, not proposed solutions, this comes later. Rank problems in terms of presumed severity.

3. Review the list of problems with @bedeho, and come up with a ranked list of solutions, in terms of complexity, that could naturally address these problems.

4. For each solution, starting with the least complex:
   a. Write a set of user stories.
   b. Create a task flow for each story: a set of actions they will do to achieve the goal of the story.
   c. Convert each task flow into a wireflow: a sequence of wireframes that give visual representations of the presentation layer where the action is performed, and what interaction leads to the next wireframe.
   d. Convert each wireflow into a user flow: a full tree of wireframes representing all paths, bad and good.

5. Get a review from @bedeho.

6. Implement into Pioneer, with @gamaranto as a reviewer.

7. Go back to the next solution in 4.

Resource

https://uxdesign.cc/when-to-use-user-flows-guide-8b26ca9aa36a