Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E: Key backup recovery key creation UI confusing #8878

Closed
matthijskooijman opened this issue Feb 22, 2019 · 1 comment
Closed

E2E: Key backup recovery key creation UI confusing #8878

matthijskooijman opened this issue Feb 22, 2019 · 1 comment

Comments

@matthijskooijman
Copy link

Description

I just tried setting up key backup. Part of that is optionally downloading a recovery key. Currently, this happens through a two-step interface. First, you get:

image

Then, when you click "Download", a file is offered for download and then you get:

image

When you click "Copy to clipboard", you get a similar screen.

Now, this is a bit confusing:

  • What if write down my recovery key from the first screen and do not want to copy or download it? How should I proceed?
  • On the second screen, what does "back" really do? It moves back to the first screen, but as a user that was not entirely clear to me and both options were a bit confusing.

I wonder if these two screens might just need to become a single screen? The info on the second screen could be included in the first screen as well (partly it already is). Even more, "Your Recovery Key is in your Downloads folder" is not even generally true and heavily depends on OS, browser and configuration.

Version information

https://riot.im/app
matrix-react-sdk version:
riot-web version: 1.0.1
olm version: 3.0.0

@matthijskooijman matthijskooijman changed the title Key backup recovery key UI confusing E2E: Key backup recovery key UI confusing Feb 22, 2019
@jryans jryans changed the title E2E: Key backup recovery key UI confusing E2E: Key backup recovery key creation UI confusing Apr 12, 2019
@jryans jryans removed the Z-UI/UX label Mar 9, 2021
@kittykat
Copy link
Contributor

I'm going to close this for now as the UI has changed significantly since this issue was filed. Please create a new issue for the current UI with details on how that could be improved if you feel that there are further improvements to be made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants