List of user experiences

Roger Taylor ([e-mail])

Abstract

This document is a curated set of relevant and high level user experiences to aid as a reference for developers.

Motivation

When I ask for a use case what I mostly get is a higher layer of the solution, not what I consider a use case. What I am asking is who is going to use the thing you are proposing and how will they use it. I want to see the range of user experiences that it is perceived as being employed for. If you have gone away and worked on a thing you want people to use and you do not know the user experiences it needs to be usable for, how can you have a relevant picture of the requirements for things of this type?

If there are user experiences that are common to different projects that developers will be working on, then it should be possible to maintain a list of them. And it should be possible to do so in a way where developers can come to the list and see well defined user experiences and to gain a higher level understanding of what they are solving than they may not have already had. It is not intended to exhaustively add anything people can think of, but the curated set which Roger thinks are of value.

Perceived value:

• Identify additional user experiences you want to provide.

• Gain a higher level understanding of the variety of user experiences.

• Provide common definitions of user experiences and any nuances worth also defining.

It is envisioned that this document will start with simple definitions and through collaboration be expanded. Are these relevant user experiences? Let's talk about it somewhere and flesh out this document.

User experiences

Payment

Implementation details are hopefully limited to those necessary to illustrate the context of a given user experience. Because we are talking about Bitcoin SV, the implication is both parties are using digital devices with wallets. Maybe Alice as the seller is using a desktop or tablet, and Bob is using his on-the-go wallet on his mobile phone. Maybe Bob and Alice are using P2P wallets, or they are using wallet as a service apps. Those things can be factored into expansions on a given user experience to give a pcut

In-person

Alice and Bob meet. Alice is selling eggs. Bob wants to buy eggs. Alice gives an invoice to Bob. Bob pays Alice. Alice gives Bob the eggs once the payment is received.

Web store

Alice has a web site where she has products listed. Bob adds some items to his cart and then checks out. The web site displays an invoice to Bob. Bob pays it. Alice sends the products digitally or physically once the payment is received.

Email

Bob knows Alice from a contact of some sort. He emails her and asks her about something. Alice sends him a link to an invoice. Bob clicks on it and pays it. Alice sends the products digitally or physically once the payment is received.

Automated / recurring

Bob has a recurring payment to Alice. Bob sets it up and authorises pre-funding of some kind and the schedule at which it should be paid. Alice gets her payment on time regardless of Bob being connected to the network or needing to authorise the payment at the exact time the payment is delivered.

P2P identity exchange

Even if we had usable integration of government identity as a tool that can be employed where necessary, it would still be extremely valuable to have non-governmental or P2P identity. These experiences are intended to illustrate the set of applications, agents or services that could be made available to users.

Public identity

Alice has a web site that everyone knows belongs to her. She can generate a public identity and put the identity packet for it on that web site. This can be used for whatever operations she allows with given constraints.

Referral

Alice knows Carol and wishes to put Bob in contact with Carol. Alice shares Carol's identity packet with Bob, giving him the ability to know that he is interacting with Carol and select details about her.

Proof of referral

Carol rejects contact from David who has obtained her identity packet but has no proof of a referral. Bob however got a signed referral from Alice, and Carol's wallet verifies this, by confirming Bob is referred by Alice, who is on Carol's whitelist.

References

None.