Open questions from the slack channel:

What are the plans for recruiting? ToIP members or a wider group? (note: the current survey questions indicate a wider group, but would like to confirm)

Using the linux/toip channels to industry but asking for it to be shared amongst colleagues, customers, friends and family to broaden the pool of responses.

What number of respondents is the survey aiming for?

Will the survey tool used offer logic (to provide additional questions based on prior responses)?

Yes ideally - possible in google forms and survey monkey

Review the comments in the document: research questionnaire.

Andrew Slack  - Snr Strategic Designer at SICPA

Bentley Farrington  - Previously at SICPA with long term experience in identity space

Ryan Koble  - Entida, Colorado building software for Farm Workers, including a wallet to interact with enterprises

@altanel - UI/UX Designer freelancing for YOMA, working on SSI products and a wallet

Vision

Mission: To enable consistent, accessible and trustworthy data exchange experiences for all,
and to make it easier for those designing and developing in our community to implement wallet based interaction design.

Why: The experience and security of any system operated by people depends on the information conveyed through user interfaces, the response of the users, and the interpretation of their actions. Existing interaction patterns in wallets tend towards visual-centric models and rely on inconsistent representations and interaction patterns. Trustworthy data exchange is a foundational building block in the infrastructure of modern society, for it to function as a public good it must be available and accessible to all.

How: Create a living repository of resources for community that:
articulates opinionated principles on trusted interaction mechanics 
highlights existing standards and examples 
recommends research-backed best practices (potentially the foundation for standards or certification) 
identifies new patterns to unlock novel experiences

1.  Initiation
   1. Consensus on vision, mission & process
2. Problem Definition
   1. What existing or emerging interaction rituals should we learn from or seek to understand?
      1. What cultural differences can we identify?
      2. How might we interact with wallets peer-to-peer, in the meta-verse, through a browser, in passive exchange,...
   2. What do we mean by wallet based interactions? What is the scope we want to address in this TF?
      1. Wallets, wallet wrapping applications, agents & associated services balloon to a whole basket of functionality.
   3. What are the challenges?
      1. Sense of control
      2. Decision making ability of individuals - especially in a credential rich future
      3. Tensions between holder, agent, custodians, ...
   4. What existing work is out there?
      1. eg Accessibility standards, research into consent mechanisms
      2. Other WGs needs or developments
      3. Ongoing wallet work (OWF, EUDI,)
         Bentley Farrington  - we should go for a limited scope to begin with. Archetypical user journey and associated interaction patterns with that - standard presentation requests and response. Go for the low hanging fruit first.
         Judith Fleenor generic interaction patterns, does the ceremony stay the same in different environments or context though? Bentley Farrington zoom levels of interaction pattern, there are transversal patterns across  different ceremonies. Start specific, then drive wider.Andrew Slack do we shorten this first phase and condense it or have this data gathering exercise run alongside other workBentley Farrington wallet tours! Reverse analysis of why wallet builders are making decisions they are in creating user focussed wallets. Should we focus on end users or issuers?Judith Fleenor invite to our TF to give us an overview.@altanel has done a competitor analysis on miro, and identified designers. Will follow up to request they join and present to us.When we are ready a blog post and announcement at all members could be the route to gather voices from across ToIP. Sooner rather than later. March 15th ideally.
3. Requirements
   1. Use cases and contextual scenarios to address.
      1. Payment for groceries, stop and search, enter a legal agreement, share medical records, buy a house, cross border..
   2. Interaction types to address
      1. Social interaction types (cooperate, exchange, coerce, compete, conflict..)
      2. HCI (instruct, converse, manipulate, explore)
      3. real-time, virtual, mixed-reality...
         Bentley Farrington this isn't being explored in the community at the moment, thinking about 'modifiers' that impact user comfort. How should a software adapt to or support in these contexts and situations? To what extent should wallets direct users along safer pathways in these contexts? How does that affect agency?
         How do we make this thinking useful for others in the ToIP ecosystem - how does that become useful to, for example a product owner?Judith Fleenor my first wallet on my mobile asked me to scan a QR code but I only had my mobile device. The context made it completely unusable - where do interaction patterns breakdown?
         We should be stress testing patterns in context.Bentley Farrington use the wallet tours to gather info about how they are overcoming these challenges today.@altanel how to bring wallet flow into the chat flow, for example messaging apps, or communicating with ChatGPT. What is not going on yet in the space, anticipating changes.
4. Design Principles
   Opinions to drive decision making and ensure consistent implementation.
5. Proposals
   
   1. Foundations
      Guidelines for core elements - sensory feedback, language, interactive states, ...
   2. Macro patterns
      Task oriented interactions
   3. Micro patterns
      Component level interactions
      
      --- DELIVERY of v1.0 ---
      
      
6. Consolidation
7. Working Drafts
8. Public Review Drafts
9. WG Approved Draft
10. ToIP Approved Draft

Proposal

• Working session - what is the scope of 'wallet' we want to address?
  • Use scenario building tools to start answering this question

• Start data gathering for problem definition! Build a collage of interactions. This will be ongoing work, perhaps we should get into the rhythm of opening or closing with a show&tell?
  • Examples of wallets, interactions
  • Challenges from those we work with, human stories, project insights, ...

Bentley Farrington start with a show & tell - work out which elements are most important and relevant for us.

Ryan Koble will bring in examples from entida

@altanel will show wireframes of wallet she is working

Judith Fleenor March 3rd deadline for blogpost. Blank template shared. Andrew Slack and Bentley Farrington to draft.