[INFO - DISCUSSION] Lightning UX challenges

[cygan]

in this thread i would like to illustrate the following 3 ux challenges that can arise in the lightning network with these 4 slides and also show you the solutions for them.
these are the 'zero configuration', 'rebalancing channel' and 'inbound capacity' challenge. there are numerous challenges that remain in implementing the lightning network as a global payment solution for BTCitcoin, and also various ways in which existing and future technologies can overcome them.
this topic or thread is also intended to stimulate discussion



https://twitter.com/BTCillustrated

[1714823470]

1714823470

[1714823470]

1714823470

[DaveF]

Not 100% OT here but it does being up the point of development in different environments with different teams.
From the developer of Zap Android

https://github.com/michaelWuensch/BitBanana/blob/master/docs/REBRANDING.md

Zap Android was just one implementation of the Zap family, which consists of Zap Android, Zap iOS and Zap Desktop. All three implementations are based on their own code base and are each developed and maintained by different developers. The features that these implementations offer are also not identical. Some are present in one, but not in the others. However, because all three implementations are known as Zap, users confuse information about one implementation with others.

So when we think of something like automatic rebalancing of channels, we can have 3 people with the same 'wallet' called Zap that has the process done / implemented 3 different ways because one is on Android, one is on iOS and one is the desktop version.

If it's all done in the background and works, it's great. If something goes wrong and people are trying to help, now and Android user trying to help an iOS user is getting frustrated because it's a different product with the same name. Up until I saw the message on my Zap for Android, I had no idea that it was not the same people working on the different versions.

-Dave