decentpatterns
add peer introduction pattern #23
This PR is intended to kick-start the co-creation of the Peer Introduction pattern as discussed initially in #23.
I'm still happy to jump on a synchronous call if you like, @bumbleblue.
My notes from today's meeting, please add / correct as you see fit @bumbleblue, @cafca, @kirakirawes.
It seemed helpful to separate the following two:
- Proposing to (newly onboarded) peers a list of potential peers they likely already know from other contexts (face-to-face, other apps) and might thus want to be connected with. Here, a list of users where a batch of proposals / offers can be composed quickly seems to be a desirable UX.
- Proposing to two peers that are unlikely to know each other already seems to require more attention in terms of a personalized introduction message and potentially custom choice of alias (either specified by a users as "how do I want to be introduced to others" or provided with good judgement by the introducing party). This fits more to the current mockup.
We also spoke about the difference the application context in which this pattern is used might make. Whether it is a more public list of subscribers scenario, or e.g. a very personal and private messaging context.
Potential examples for introductions or recommendations: Good Reads (we're looking for example screenshots)
It was pointed out that introductions could already happen as part of an invitation flow, so that new users already onboard connected to recommended peers.
Jumping back and forth between projects I notice that I conflate users, contacts, peers. Is there a glossary for the decent patterns library or a feeling for where to differentiate and which one to talk about?
Users seems to be generally bound to an application context without any implications about social or technical interconnectedness. However, peer and contact seem to overlap a fair bit.