22D/ UX for SSI - Applying Design Principles to SSI

UX for SSI - Applying Design Principles to SSI

Thursday 22D

Convener: Josh Welty

Notes-taker(s): Josh Welty

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps: 

High Level Brainstorm: Problems and Ideals with verifiable credential interactions

Problem:

Language of SSI - a barrier to understand

"presentation" - everyday user doesn't know what that means

"connection" - persistent?

Management/organization of credentials

making sense of how connections and credentials interact

Users don't care about connections

Why do I need to engage with the wallet at all? Why do I need to leave my workflow to use a separate wallet?

Selling the benefits of using a wallet -

Ethical mission of SSI - is it obvious enough to encourage users to use SSI (do we want to rely on the user to care?)

Ideal:

Interface would have the next step in the workflow obvious - only show things that make sense in that context.

We have to think of the user's workflow and build around that

Maybe not letting them know they're using a wallet?

Familiar questions, not jargon (when sending information)

Workflow opens the wallet - I don't know it's a wallet, my credentials work for me in the background

As much control/information as the user would like