keybase / keybase/keybase-issues
Chat with not yet keybase user via email handle has UX problem
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
When I discovered that keybase allowed me to start a chat with someone not on keybase just via their email, I thought it was brilliant idea! Unfortunately it turns out process of onboarding that new user is not very smooth which leaves new user with a feeling of it being broken. Below I'll try to describe how it went in my case to outline the problem:
- I decided to get some conspirators onto keybase, to form a team and go about conspiring.
- I start a new chat and add all of their emails. New chat even offered me to create a team!

- **problem** is however that after I entered a team name and clicked "created team" button it created a new team **unrelated** team. Chat thread does not appear under the team and I still see that prompt to create a team.
- I also had another convenient message suggesting me how to summon my conspirators

- I did provided them with a link, they installed an app, created an account with the emails I have had there, but **were not able to see the chat**.

- So we kept on wondering why we were able to chat in keybase still without my conspirator being able to see the chats I've started via email

- In the end we have figured out that reason why conspirator was unable to see those chats is because "email address had to be made searchable"

-----------
I think onboarding by just starting a chat with someones email can make a huge difference if the process is smooth, but if it's full of pitfalls like in our experience it can have backfire effect.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the email-handle chat onboarding flow described in the issue, including team creation and making an email address searchable. Compare what the inviter and newly registered participant see in the attached screenshots; done means the created team is associated with the chat and invited users can find and open it without discovering a hidden searchability requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100