search

btcpayserver / organization

Open-organization, meetings, calendars, project management
https://btcpayserver.org
17 stars 3 forks source link

Design Call #7 #33

Closed Zaxounette closed 3 years ago

Zaxounette commented 3 years ago 
Date: 2021-04-29
Time: 5:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-04-29 17:00 UTC

Agenda

Other items TBD. Comment below to add items.

Check your timezone

https://everytimezone.com/s/cb291696

Join the call

https://meet.jit.si/AssistantToTheRegionalJanitorsOffice

Calendar invite

Subscribe to the BTCPay Server calendar. More info here.

dstrukt commented 3 years ago

Agenda items:

has there been any work on the UX of the wallet signing process? because right now we have dropdown to select how to sign a transaction I would like to replace this with a proper wizard like the setup ok, was asking because for next release (not this one), I plan to work on adding RBF and as part of the flow, I will need to redirect the user to this wizard

If time:

Will update if I think of any more.

Zaxounette commented 3 years ago

or I could relay this to @Zaxounette

I'll take notes, as usual, so even if pav isn't here, he'll have notes to work with.

dstrukt commented 3 years ago

that'd be great, thank you!

Zaxounette commented 3 years ago

Design N°7 Notes Attendees: @dennisreimann @dstrukt @pavlenex @Zaxounette

Bootstrap v5: Integrating v5 is more work than anticipated, but it's advancing nonetheless. There are still some test failure that appeared while working on the integration process. These failures still need to be explored for resolution, but are not concerning. As for the actual integrations, some classes need to be replaced still, and a follow up between Dennis and Dstrukt will be done regarding component migrations.

Figma organizational change: Discussion on a proposal to split the Figma pages further than they are for organization purposes. Splitting between users, possibility to create teams, and split between views. This leads to discussing the question of upgrading tier in Figma to benefit from this organizational change. Pavlenex will reach out to Figma to explore possibilities for open-source pricing.

Payjoin as default: Some NACKs have been given on the current open PR. A counter proposal is to include the Payjoin toggle in the Wallet Receive tab. This is felt like we would bury the option and users wouldn't even know of the option, less think to disable it if they wish if it's placed in that tab. The Payjoin option is only useful for hot wallets, so it makes sense to have it in the hot wallet setup and not in the general wallet overview where non-hot-wallets could be used while still having the option visible.

Another point has been brought up: Regulatory issues have to be considered. So having this option visible and not buried, even if toggled by default, should be a conscious choice by the user for having Payjoin.

The bracket in the wallet overview quickly be filled with too much information. We have to determine what info should reside in it and what info should not. Is Payjoin status important enough to go in bracket ?

This particular items needs more discussions.

Proposal to further reduce number of clicks on LN wallet setup workflow: A simple NACK. The intention behind the proposal was to reduce by 1 click the LN wallet setup, but the proposal doesn't take into account user education, user possible confusion as to what default setup on toggle is, and taking into account how plugins will interact on the future view of wallet setup.

Wallet signing process conversion to wizard: The wallet signing process as per Nicolas's requests should be redone. This particular view is the process in the Wallet > Send tab. Dstrukt will get inputs from Nicolas and Kukks as to what exactly should be included in such a wizard, on top of the obvious settings and options already included in the current view.

Website code refactor: Is discussed a possible refactor of the website. What has been currently determined is that the website's backend can be updated and take advantage of the Bootstrap v5 migration as well as update it as per the design guidelines. A main goal of this can be viewed as back-end code cleanup and load optimization for users.