Is this just for the Lightning gateway? I’ve been reconsidering the decision to display information about the gateway. In the ecash guide for the Bitcoin Design (npub13s5…l03e) community I’m working on, I listed the following reasons for not including information about the gateway.
Why showing gateway information might not be necessary:
1. Cognitive Overload: Most users are not interested in the technical details of how their transactions are processed. Presenting information about gateways, especially vetted versus non-vetted ones, could lead to confusion, as users may not understand what this information means or how to act on it.
2. Trust in the System: In well designed systems, users trust that the service has selected the best pathways for their transactions. By not overwhelming users with technical details, the system can reinforce trust that the backend will manage their transaction securely and efficiently without their intervention.
3. Bettter UX: The goal of good UX is to make the user experience as seamless and intuitive as possible. Introducing gateway information may disrupt this flow by adding unnecessary steps or considerations that the average user doesn’t need to think about.
---
It sounds like you’d find this information helpful. Do you think the average user would feel the same, or do you think it might add confusion?
erik
npub1zq…fcqrs
2024-09-02 17:54:13
in reply to nevent1q…uxcv
Author Public Key
npub1zqsu3ys4fragn2a5e3lgv69r4rwwhts2fserll402uzr3qeddxfsffcqrsPublished at
2024-09-02 17:54:13Event JSON
{
"id": "53f9c048bbb70bc63d51d66ab6f9675fe17ab379dbfa8dd80800a2f5c1fdb718",
"pubkey": "1021c8921548fa89abb4cc7e8668a3a8dcebae0a4c323ffeaf570438832d6993",
"created_at": 1725299653,
"kind": 1,
"tags": [
[
"p",
"8c29b321d0f3c61343882ea49623e84771690cd0566e40b90f08e5d34336aaa0",
"",
"mention"
],
[
"e",
"07d40612225e1cb3cdb4e9f525fe056591e1a1ac014b50911e21f0c2ff0b2053",
"wss://relay.urbanzap.space",
"root"
],
[
"e",
"fecf1c2b1750fa5e8d2ed138e775e6caf3d048d746a1b287db1952a09f77bdec",
"wss://relay.urbanzap.space",
"reply"
],
[
"p",
"1021c8921548fa89abb4cc7e8668a3a8dcebae0a4c323ffeaf570438832d6993"
],
[
"p",
"45b1a33381db7aaf459e53ae42654f8cb2ab582a00c987daa83586763424a300"
]
],
"content": "Is this just for the Lightning gateway? I’ve been reconsidering the decision to display information about the gateway. In the ecash guide for the nostr:npub13s5mxgws70rpxsug96jfvglggackjrxs2ehypwg0prjaxsek42sqd9l03e community I’m working on, I listed the following reasons for not including information about the gateway.\n\nWhy showing gateway information might not be necessary: \n1. Cognitive Overload: Most users are not interested in the technical details of how their transactions are processed. Presenting information about gateways, especially vetted versus non-vetted ones, could lead to confusion, as users may not understand what this information means or how to act on it.\n\n2. Trust in the System: In well designed systems, users trust that the service has selected the best pathways for their transactions. By not overwhelming users with technical details, the system can reinforce trust that the backend will manage their transaction securely and efficiently without their intervention.\n\n3. Bettter UX: The goal of good UX is to make the user experience as seamless and intuitive as possible. Introducing gateway information may disrupt this flow by adding unnecessary steps or considerations that the average user doesn’t need to think about.\n---\nIt sounds like you’d find this information helpful. Do you think the average user would feel the same, or do you think it might add confusion?\n",
"sig": "840f58efec755c8e39f92170abf9be8f8e13245e0f1beca394166cc85b9b8b537fb824b0e0415bc28ec60a643157cf21364f780668b07917297bd97e0b003cf0"
}