Skip to content
This repository was archived by the owner on May 3, 2024. It is now read-only.
This repository was archived by the owner on May 3, 2024. It is now read-only.

Considering WabiSabi in the re-design #18

@ghost

Description

We are currently re-designing Wasabi UX. There is one major UX break coming up in the future, and this is the switch to the WabiSabi CoinJoin protocol. The main difference is, that now users can make a payment within the CoinJoin, and this kinda makes the design with separate Send and CoinJoin tab obsolete...

However, this new protocol is still early WIP, and we don't even know the specifics of it, so I think it is too early to focus on it just yet. Though, I think that WabiSabi will be here soon enough, so it might not really make sense to do a redesign of these core features of sending and coinjoining for the old protocol... So, too early to design WabiSabi, but soon enough to not mess with current UX just yet.

Question... Do you agree with this? Should we still change sending / coinjoining UX already now? Should we already start designing Wabisabi?

I suggest we first focus on the other parts of the UX redesign:

Question... Which one of these is priority?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions