Improve insufficient inbound capacity error message UX

[moneyball]

Description

Attempt to Request a payment.

Steps to reproduce the behavior

1. Select Request
2. Enter an amount then Next

Expected behavior

For first time users, the expected behavior is to generate an invoice that will work. However, if inbound capacity is an issue, first time users will need to be educated about this.

Suggestions:

1. For something as important as this for first time users, don't show a temporary message but instead something that requires user action to dismiss.
2. Provide friendlier language to explain the issue of inbound capacity.
3. Provide concrete next steps the user can take to solve the issue.

I think many first time users will "test it out with a friend" and then face a chicken & egg issue, where neither friend can send to each other to create inbound capacity.

Actual behavior

Temporary error message shown at top of display (see screenshot).

Screenshot and/or logs if applicable

[moneyball]

I would suggest that until better solutions come along to solve inbound capacity, that a far better initial user experience for a new user/wallet would be to recommend a few services they can use such as Lightning Spin or Y'alls.

[tanx]

Hi @moneyball. Thanks for the feedback! Generally speaking, inbound UX is still an unsolved problem right now. We definitely need better UX for error cases. Our next step is to integrate Lightning Loop and provide users with a "buy inbound" workflow. But even then, there are still some significant UX challenges to overcome for a non-custodial app.