[bisq-network/bisq] Keybase meeting Thursday, April 1st 21h00 UTC (#5378)

[m52go]

## Meeting Minutes

Agenda:
```
Today we will be following up on some topics discussed on the last 
meeting (https://github.com/bisq-network/bisq/discussions/5322) plus 
touching up on some highlights of the new release:

	A. New UI (https://github.com/bisq-network/projects/issues/49)
		+ What exactly would a new UI developer be working on?
		+ What's stopping Bisq from being a mobile or web app? A 
                  clarification on the specific vision for it is necessary. What
                  would this mobile/web app do?
		+ Why does Bisq need a new GUI? 
                  (https://github.com/bisq-network/bisq/discussions/5371)
		+ Early mockups for a new Bisq UI by @pedromvpg
                  (https://github.com/bisq-network/bisq-design/blob/master/bisq-refresh.pdf)
		
	B. New release (https://github.com/bisq-network/bisq/releases/tag/v1.6.2)
                  - API
                          + Proposal (https://github.com/bisq-network/proposals/issues/136) - this 
                            is a project that aims to bring more automated functionality to Bisq
                          + Issue (https://github.com/bisq-network/projects/issues/11)
                          + Project board (https://github.com/orgs/bisq-network/projects/17)
				
                  - Initial working on Segwit BSQ (https://github.com/bisq-network/bisq/pull/5000)
```

### A. New UI (https://github.com/bisq-network/projects/issues/49)

There was some initial disagreement over whether or not investing in a new UI for the existing Bisq software is a good move.

Some said there are other objectives which should have higher priority than a UI overhaul (e.g. reducing on-chain footprint), and many agreed, but the UI overhaul doesn't overlap much with those other objectives while making Bisq a whole lot more approachable for new users. 

Protocol development could use more hands, but finding such developers is not easy...so might as well allow the UI work to continue in parallel.

Costs for UI overall will be better known once the UI developer takes a closer look at the code through performance testing and designing the onboarding UI (these are examples of initial tasks to see how well things are working out).

Full project proposal is linked above, but some key ideas were listed in the chat:

- Assess if JavaFX is necessary
- Refactor the code to streamline future changes to the UI
- Add an onboarding flow (completely new)
- Work on improving the UI to make the client more up-to-date and elegant
    - Standardize styles and clean up inconsistencies
    - Move nav to the side
    - Rework responsiveness

Timeline:
https://docs.google.com/spreadsheets/d/1RvjngdWhKX8L47tLkEP9eiJjfSb-SyUWvHnDYZP5YcQ/edit?usp=sharing

Mockup:
https://xd.adobe.com/view/a83c2327-4730-4ec2-8938-e318b2749588-fd6f

### What's stopping Bisq from being a mobile or web app?

API needs to serve JSON to enable web and mobile use cases, which is something API developer would prefer to explore later when API is more mature and more used...but could happen sooner if it turns out gRPC-web is feasible to use.

Control of current notification apps is in the process of being handed over to a more active Bisq developer. This new developer is planning to fix a couple of high-priority bugs, but probably won't be doing any significant development on the apps.

### Segwit BSQ (https://github.com/bisq-network/bisq/pull/5000)

Initial code shipped in 1.6.0 for activation toward the end of May and full delivery in the next planned release (if all goes well).

Developer leading efforts on atomic BSQ-BTC swaps is hoping to have an update on his efforts for meeting in 2 weeks...this effort involves major refactorings, but will set the stage for a single-tx trade protocol.

---

Potential topic for next meeting: Bisq DAO privacy and improving the colored coin implementation.
- Video summary (https://arxiv.org/abs/2007.07048)
- Paper (https://www.youtube.com/watch?v=VRr-aWQpAWA)

-- 
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/bisq/discussions/5378#discussioncomment-573075
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210405/48465968/attachment.htm>