Design Call #23 - Githubissues

Zaxounette commented 2 years ago

Date: 2021-11-18
Time: 5:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-11-18 17:00 UTC

Comment below to add items to the agenda.

Subscribe to the BTCPay Server calendar. More info here.

dstrukt commented 2 years ago

Proposed Agenda, in order of importance as I see it as of this moment:

Update and discussion of @dennisreimann's progress on (https://github.com/btcpayserver/btcpayserver/pull/3091) and whatever may be surfaced/involved at this stage
Wallet/Node/Payment Method Settings aggregation and steps forward for a feasible proposal (Figma)
Invoice Views: (https://github.com/btcpayserver/btcpayserver/pull/3122) & (https://github.com/btcpayserver/btcpayserver/pull/3092)
Lightning Node Landing View Discussion (Figma)
Pay Button final adjustments (https://github.com/btcpayserver/btcpayserver/pull/3112)
Wallet View Iteration (Figma), if time
Have some other thoughts / feedback I've heard this week / El Salvador / suggestions for 1.5.0 roadmap type of stuff, but that might end up being out of scope depending how far we get, but depending, might be worth reserving 5-10 mins at the end for this.

Zaxounette commented 2 years ago

Design Call N°23 notes Attendees: Pavlenex, Dennis, Dstrukt, Wouter, Andrew, Zaxounette

Dennis presents the store centric implementation he is working on.

Includes the homepage that is now the fresh setup empty state page
Mobile
- Store switch moves to top navigation
- On mobile, having the sidebar popup wouldn't leave any space for the content
- On medium break-point
  - True for window resizing on desktop as well
We need to discuss the fact that server settings, invoices and account setting are set in "global" in the store dropdown
- Needs renaming
- Also the fact that users click on global settings and get "thrown out" of their current store has a flaw
- But on the other side those settings are global, and users that view those pages while still being in the current store might be confused as to if they are store settings or global settings
- Is discussed the the store selector and the store dashboards and global dashboard user experience
  - Namely enabling a user to know in which view they are and not be lost in them
- Idea to delete the "global" tag on the store switch and replace it with a "select store" neutral
Notification component has been moved top right, compared to the mock-ups
Currently working on implementing the left side navigation items
- Will then be able to work on the page content implementation

Is discussed the store dropdown edge-case in the case of a high number of stores

Idea of having a maximum length to the components and make it scrollable when max length is surpassed
Having the "create a store" component of the selector on the top would disrupt the flow and force users to pass that component each time they would want to change store
- Would make the component too prominent

Server settings and account settings page

Should introduce the second side-bar as horizontal for clarity
- No memory of seeing an app with two vertical sidebars

Re-introduce the global header?

Pav sees it as global settings = top header, whereas left nav bar = store specific
Most of the questions around top header might come from the confusion of the left navigation not being implemented yet
- Some hesitancy because we don't know where we're going
- Dstrukt recommends waiting a few more days after the navigation implementation is complete
- The idea of removing the header altogether was to leave more space for content

btcpayserver / organization