Design Call #18

[Zaxounette]

Date: 2021-09-16
Time: 5:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-09-16 17:00 UTC

Agenda

Comment below to add items to the agenda.

Check your timezone

https://everytimezone.com/s/2fabbb66

Join the call

https://meet.jit.si/WeDaBestCrewEVA

Calendar invite

Subscribe to the BTCPay Server calendar. More info here.

[pavlenex]

Proposed Agenda:

• Figma migration update from @dstrukt
• https://github.com/btcpayserver/btcpayserver/issues/2619
• https://github.com/btcpayserver/btcpayserver/issues/2783
• https://github.com/btcpayserver/btcpayserver/pull/2804 @pavlenex
• https://github.com/btcpayserver/btcpayserver/pull/2878
• https://github.com/btcpayserver/btcpayserver/pull/2882

If time allows:

• Unification of Payment Request and Invoice relevant discussion on Mattermost
• Unification of Apps and Plugins relevant discussion on Mattermost
• https://github.com/btcpayserver/btcpayserver/pull/2876
• Footer cleanup (remove logo credits, add social and gh icons to footer)
• Remove reference to Slack

[dstrukt]

• Refund flow

Pull Payments Description (assign):

• https://github.com/btcpayserver/btcpayserver/issues/2625

• Improve Rescan wording:

Time permitting:

• Could show some improved views for discussion
• https://github.com/btcpayserver/btcpayserver/issues/2858

[Zaxounette]

Design Call N°18 - Notes Attendees: @Zaxounette @pavlenex , @dstrukt , @dennisreimann , @wouter

---

Discussing a bit the docs visual improvement, and separation of blocs and guides. To be discussed in details in a separate call.

---

Figma restructuring and migration:

• We now have a pro license on Figma, the free version was very restricted
• Structured pages are now in the Figma
• Changes in one project now propagate across pages and projects
• Thinking of having all the images in the docs being mapped in Figma for easy reference and location

---

Empty state improvements

• Currently, when we archive an invoice, we hide them visually
  • If all invoices have been archived, do we default back to empty state?
  • We should keep the search, because of the edge-case of un-archiving invoices
• The point of these states is for new users arriving to those pages for the first time, to make clear what they need to do
  • If user has archived all their invoices, they have already seen the empty state at one point, and are not a "new user" anymore
• Case of not having a store
  • People are overwhelmed with the BTCPay concepts and don't know what to do
  • Dashboard fixes this, in part
  • We have the main page that has "wallets" but they can't user a wallet before having set up a store with a wallet inside
  • Logic of creating a wallet first and them tying a wallet to XYZ store
• Potential solutions
  • Hide menu items and leave store creation
  • How do we tie store and wallet creation?
    • Create a wizard inside a wizard?
  • Auto-create a store on first user connexion?
  • Once store is created, they are left with creating a wallet
  • Conceptualise apps, payment requests, general store settings under the store itself
  • Enables us to clean up the top navigation
  • Enables us clarify the global navigation for users new and old
  • Is a big change for users, but can be implemented fairly easily Early solution mockup :

---

Pavlenex showcases Kukks' work on Lightning Addresses and LNURL

---

Discussing the UI and possibilities of the LNURL cart/shop printable view.

• Early discussion
• Idea of leaving the option to the user to have full descriptions, price, feature image, etc... for the print, instead of only product title and price with the QR code.