Redesign Lightning wallet connect UI

[pavlenex]

The goal of this issue is to bring in discussion around potential UI improvements, suggested improvements have to be discussed, ironed out, so this issue shouldn't be worked on yet.

Context: Our lightning wallet UI is quite different than our create a wallet UI. The pill UI doesn't really allow us to showcase a great amount of options that are possible, and it seems that with plugins a whole set of connect external lightnign wallets is coming into the place (Breez, Alby, Blink, LDK).

I think as our selection of options to use Lightning (in a custodial, or self-custodial way) grow, our UI has to cater for those options and guide users through setting up an adequate one.

Currently: Our UI for lightning looks like this

Our UI for creating an on-chain wallet is way more accessible and guides users to tailored options and will help us unify the UI components a bit more.

It can be: (obviously we need to discuss these),

• Start a lightning node
• Deploy LN node
• Deploy LDK -Deploy Breez
• Connect a lightning wallet
  • Connect via plugin (where we showcase all lightning plugins under payment method category, even if pliugins are not published)
• Connect external node (advanced)

[dstrukt]

Makes sense to tackle this, it has been a while since we've touched this page and many of the wallet views. Will make a note to discuss in the next design call!

[DoktorShift]

I Just searched for an open issue to connect lnbits as a funding source for the lightning payments inside btcpay.

Nice to See you are working on solutions to accept more Implementation options for the ln payments then the actually Provided Options (custom node and internal node)

Should i open an issue which points directly to the usecase to connect a lnbits Wallet as funding source?

Cheers

[dstrukt]

@DoktorShift Sure, either works - if it's easier, you can drop in this Issue as well!