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

Improve UX to migrate normal account to keycard account #12336

Closed
guylouis opened this issue Jul 22, 2021 · 3 comments
Closed

Improve UX to migrate normal account to keycard account #12336

guylouis opened this issue Jul 22, 2021 · 3 comments
Labels
feature feature requests

Comments

@guylouis
Copy link
Contributor

guylouis commented Jul 22, 2021

Problem:
when a normal (his keys are stored on the phone) user wants to migrate his account to a keycard then, he is been taken through this flow
https://www.figma.com/file/Z2T0QW0TgIrJEeTjgBidAG/Untitled?node-id=0%3A1

image

Primarily, this flow has been considered

  • hard to locate for users that want to migrate
  • complex (naming and copy are not obvious)
    Also
  • the choose storage screen is not providing any choice to the user so it could be removed or simplified to an information screen

How to improve this?
This flow needs design eyes to simplify the user experience
An idea would be to add in the '...' screen an entry which would be 'move account to keycard' and which by default would keep the database, it would thus be much simpler for the user to understand and proceed. MOre advanced users could still go through 'manage keys and storage'

cc fyi @bitgamma @churik

@churik
Copy link
Member

churik commented Sep 22, 2021

I believe that can be closed after #12395
@guylouis please reopne if still relevant

@churik churik closed this as completed Sep 22, 2021
@bitgamma
Copy link
Member

I think it would be nice to reopen this because this was about simplyfing the flow (both from logged in and logged out state) and making it easier to find

@churik churik reopened this Sep 22, 2021
@churik churik added the recheck label Dec 5, 2022
@churik
Copy link
Member

churik commented Dec 5, 2022

closing due to re-design, label recheck added for future re-consideration

@churik churik closed this as completed Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature feature requests
Projects
None yet
Development

No branches or pull requests

4 participants