The error message says “Failed to find route” which is simple but not user-friendly because it doesn’t address the problem they are having, so they comment under the invoice, “It didn’t work.” and this has the potential to discourage people and make them think Lightning doesn’t work well, because they don’t understand what went wrong. A more descriptive message would go a long way here. It helps to put yourself in the shoes of the newest of users who don’t know what routes are, they just see something that looks broken.
Discussion
We could put "failed to pay invoice" but that's the same thing with less info. The alternative you suggested is just wrong, not sure if there is a better alternative.
What was wrong, the phrasing? Help me understand because as a user it seems very opaque.
I already explained here
https://damus.io/note1lspt5cfk5m0j7ljspt5j5falhned2z74ar2l68jh96wxc286pkgswd98x2
I understand, but curious as to why it couldn’t say:
“Could not pay the invoice. There is no route, or it may have been paid.”
That way you’re not giving an absolute. Just thinking of user experience.
I’m just trying to solve this UX problem:
nostr:note10lvqwsw8wkf5ev8s6hzj53esyg8ewyuw3e3jpl2aqt9dvxyurluqjlml5p