Design Call #24

[Zaxounette]

Date: 2021-12-16
Time: 6:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-12-16 18:00 UTC

Agenda

Comment below to add items to the agenda.

Check your timezone

https://everytimezone.com/s/724edb3d

Join the call

https://meet.jit.si/DesignCallsROCK

Calendar invite

Subscribe to the BTCPay Server calendar. More info here.

[Zaxounette]

Pushed this call 1 hour latter due to popular demand.

[dstrukt]

Thank you for updating @Zaxounette! <3

Proposed Agenda:

@dennisreimann

• Current State of Store-Centric demo to break into discussion.
• Discuss and explore "Global"/"Store" sidebar component, based on current PR state, as a group.
• Sidebar UX discussion, current state, shortcomings, etc..
• Update on LNBank integration in new S.C view, will it be in 1.4.0?
• Refactoring (https://github.com/btcpayserver/btcpayserver/issues/3183), if worth commenting on.

@dstrukt

• Lightning Node View
• Payment Settings (LN & Wallet)
• Wallet View
• Like last call, the goal, from my POV at this time, should be to make decisions on what's been done, and unblock @dennisreimann to keep killing it.
• Various UI/UX, some covered in the above topics (https://github.com/btcpayserver/btcpayserver/issues/3180)

[Zaxounette]

Design Call N°24: Attendees: @dstrukt @dennisreimann @pavlenex @Zaxounette

---

Discuss the store-centric changes and decide what we need to get it into a release.

• Release date is undefined, probably after the end of year pause.
• 1.4.0 regarding the store-centric PR will not contain the dashboard
  • A few ideas around where the default view would land on while the dashboard is constructed
• Dashboard
  • Global level or store level only?
  • Users would be confused at first with the context switching
  • But global state still needed for global invoice list and plugin list
  • Technical hurdle that we should store the last visited store as a cookie or something
  • We need to test these changes with outside individuals to get a feel on them at the broad user-level

Action Items:

• Add this branch to the testing instance
• Pav to facilitate usability testing and get broad user feedback
  • We will need different typology of users
  • Low volume/high volume
  • Regular user/power user
  • Etc ...

Minimum viable dashboard:

• Store level only as an MVP
• Add some low hanging fruits
  • Tackling the empty state in case nothing is set up (wallet for example in the case of a fresh instance)
  • Add invoices and some simple stats to the view

Summing things up:

• The home page would be replaced by an MVP global dashboard
• The store default views would point to store-level MVP dashboards
• Further iterations on the dashboards will be worked on after 1.4.0 to improve them overall

[dennisreimann]