Wasabi is using a media player-like approach to control CoinJoin operations: play, stop, pause, and progress bar. There is also a message box that displays the latest status. This is called MusicBox control. Unfortunately, this is a source of confusion in many cases. The goal of this Quest is to dismiss the confusion by refactoring or even replacing the control.
π Specification, Scope, and Features
UX research. Collect feedback about MusicBox.
Collect all the business logic states and phases and actions (like override plebstop, etc.) and draw a graph to see what kind of operations you need to deal with.
Reset your brain and look at CoinJoin as a grandma. How could Grandma operate this?
Figure out what is important to the user and what is not. Remember displaying unimportant information will just cause confusion and questions on the support side.
Create Figma plans.
Collect feedback and finalize.
Implement the new UX to the software.
βοΈ Motivation
MusicBox continuously causes confusion on the user side.
Not looking good - scattered.
Placement?
π Rationale
The first task is to investigate the problem deeply and analyze user feedback about the music box. After that setup a model of how the user should control CoinJoin - that is easy to understand. After that figure out a UX. try to include special cases as well. Do not display multiple information on one surface - reduce the cognitive load by having only one question or information - select the most current one. For example, if PlebStop kicked in then only display information about that. For example: if your balance is low, do you want to continue CoinJoin - Yes or No? If these ideas are there, start drawing using Figma. Ask feedback from the team and try to sit plebs in from of your design and see how they are trying to use it. Talk to the UI team and start the implementation.
π Backward Compatibility
It is important to have something that old users would be able to use immediately. This could be improved by having similar symbols on the buttons - but this was just an example - the point is that extra effort is required here as well when creating the new design.
π Reference Implementation (optional) or issues
There was only one vote on this, so I revoked it from further participation as the author of the quest. Pinging @wieslawsoltes FYI. Maybe in the next releases.
π Preamble
Harmony in the music by @molnard
π TL;DR - Too Long, Didn't Read
Wasabi is using a media player-like approach to control CoinJoin operations: play, stop, pause, and progress bar. There is also a message box that displays the latest status. This is called MusicBox control. Unfortunately, this is a source of confusion in many cases. The goal of this Quest is to dismiss the confusion by refactoring or even replacing the control.
π Specification, Scope, and Features
βοΈ Motivation
π Rationale
The first task is to investigate the problem deeply and analyze user feedback about the music box. After that setup a model of how the user should control CoinJoin - that is easy to understand. After that figure out a UX. try to include special cases as well. Do not display multiple information on one surface - reduce the cognitive load by having only one question or information - select the most current one. For example, if PlebStop kicked in then only display information about that. For example: if your balance is low, do you want to continue CoinJoin - Yes or No? If these ideas are there, start drawing using Figma. Ask feedback from the team and try to sit plebs in from of your design and see how they are trying to use it. Talk to the UI team and start the implementation.
π Backward Compatibility
It is important to have something that old users would be able to use immediately. This could be improved by having similar symbols on the buttons - but this was just an example - the point is that extra effort is required here as well when creating the new design.
π Reference Implementation (optional) or issues