[bisq-network/projects] Implement new-user-onboarding and new user interface design (#49)

pazza notifications at github.com
Mon Mar 29 00:27:35 CEST 2021


## Description
Implement new-user-onboarding and new UI design as discussed in #47  

## Rationale
Bisq is a P2P exchange that is accessed via a software client that while extremely functional has remained largely unchanged from a user interface and user experience perspective.
In order to increase the accessibility of Bisq for new and existing users the user interface and user experience should be redesigned. 

### Goals

The goals of the redesign should be to:

- Enable Bisq to capitalize on it's clear competitive advantages
- Improve user conversion rates
- Increase user loyalty and retention
- Increase growth in number of users
- Maximize revenue for the DAO
- Reduce support issues and associated costs
- Improve the trading experiences for users
- Enable is to be designed in a way that meets a variety of user needs and requirements


### Why now?

The UI designs, being done by @pedromvpg, have in a state nearing completion for a while, the barrier to implementing them was lack of UI developer resources. @chimp1984 has recently been in touch with a developer that is keen to get involved in a UI resign. Having a dev in place and most of the designs already complete means it is a good time to start a UI redesign.  

The risks of not doing it now are that Bisq may struggle to have the UI developer resources at hand to implement the project. 

## Criteria for delivery
The project is fairly large and will be implemented in the following stages:

- Coding and onboarding stage
- Client redesign stage
- Home redesign stage
- User feedback and review stage

A rough project plan can be seen here: https://docs.google.com/spreadsheets/d/1RvjngdWhKX8L47tLkEP9eiJjfSb-SyUWvHnDYZP5YcQ/edit#gid=1115838130

### Coding and onboarding stage

The first two aspects will be:

1. Performance test FXML vs Plain Java (there is a certain amount of coding needed as recommend by @ripcurlx prior to changing the design)
2. New user onboarding process, see @pedromvpg's designs here: https://xd.adobe.com/view/a83c2327-4730-4ec2-8938-e318b2749588-fd6f/

The reason for the above two being first is that they can be designed and implemented first without effecting the other aspects of the client.

### Client redesign stage

Once the above have been successfully completed the project will move into redesigning the user interface of the following sections:

- Menu structure and layout
- Create-offer and take-offer views
- Portfolio section
- Funds section
- Accounts section
- Settings section 
- DAO section
- Markets section

The current designs for the above by @Pedromvpg can be seen here: https://xd.adobe.com/view/b01dfd7a-3f79-4744-8df9-08394d2ea1ea-e54e/grid/

The above sections will be more clearly outlined following completion of the intial stage.

- Home redesign stage

It is expected that once the client has been redesigned it will be necessary to resign the home screen to pull in the necessary data to make trading on Bisq an effective, efficient and satisfying experience.

- User feedback and review stage

The final stage will be allow for a period of user review and feedback before implementing any changes.

## Measures of success

The success of the project will be measured against the goals:

### Objective measurements:

It is preferable to measure goals in objective terms. Goals that can be measured objectively include:

- Are Bisq's competitive advantages clear?
- Is Bisq seeing an increased number of peers connecting to the platform
- Is their an increase in trading fees?
- Is their a decrease in support enquiries relative to number of users

### Anecdotal measurements

Where goals can not be measured objectively due anecdotal measurements will be used to assess the changes in:

- User conversion rates
- User loyalty and retention
- Trading experiences for users
- The design meeting a variety of user needs and requirements

## Risks

Changing the way users interact with Bisq will not come without risks.

I will defer the the devs for risk in implementing a new UI.

Other risks to be considered are: 

Risks of project being stalled / delivered incomplete. This will be mitigated by breaking the project into sections and ensuring that any work delivered can be picked up by another contributor. 

Design is subjective, there is the risk, or reality, that not all users are going to prefer a new design. This risk will be mitigated by trying to involve users from the outset and giving users the opportunity to express their opinions and input on any new designs.

## Tasks

- Confirm UI dev is happy to take on project.
- New UI dev to complete the performance test FXML vs Plain Java (to be reviewed by @ripcurlx).
- @pazza83 and @Pedromvpg to confirm onboarding designs.
- UI Dev to complete onboarding designs.
- @pazza83 and @Pedromvpg to confirm client redesigns, and get feedback from Bisq community before finalizing designs
- UI Dev to complete client redesign.
- @pazza83 and @Pedromvpg to confirm home section redesign, and get feedback from Bisq community before finalizing designs.
- UI Dev to complete home redesign.
- Bisq community User feedback and review stage.
- @pazza83, @Pedromvpg and New UI dev to implement any changes

### Roles

- @pazza83 will project manage
- @Pedromvpg will complete designs
- New UI dev will complete dev work
- @ripcurlx will oversee new UI dev with regards technical aspects 

## Estimates

The estimates will be broken down into the various stages.

Each section will have confirmed costs from all contributors involved in the various stages.

The costs for the initial stage of Performance test FXML vs Plain Java will be confirmed by @ripcurlx and the new UI dev.

@chimp1984 previously put the cost for the whole project somewhere between $30-60k USD. 

## Notes
The new UI dev is new to Bitcoin and the DAO model.

@chimp1984 previously made the following offer:

> To not make that a barrier I will offer to prefund his work so he will work as sub-contractor for myself and I will do the compensation requests for him (if anybody else want to play that role please get in touch). Mid/long term he should fade into the normal DAO contributor model. I also made clear that we are looking for a long term commitment and even if there might not be enough work for a fulltime UI developer that he stay committed for at least 10-20 hours so we can rely on a long-term UI/UX expert.

I have offered to pre fund the work of the UI dev so that the new UI can be completed. It is still to be confirmed how this will work exactly but I think in principle myself, the new UI dev and other contributors are happy with this model, although progressing to a DAO model for the long-term would be preferable.  


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/49
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210328/9b6a9f29/attachment-0001.htm>


More information about the bisq-github mailing list