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

Onboarding - Remove step to choose profile name and update password step #21567

Closed
ilmotta opened this issue Nov 5, 2024 · 4 comments · Fixed by #21715
Closed

Onboarding - Remove step to choose profile name and update password step #21567

ilmotta opened this issue Nov 5, 2024 · 4 comments · Fixed by #21715
Assignees
Milestone

Comments

@ilmotta
Copy link
Contributor

ilmotta commented Nov 5, 2024

Feature

Description

From the new "Create profile" screen, when the user presses "Let's go", the new profile creation flow should start at the password creation step.

Out of scope

Acceptance criteria

  • Remove the step allowing the user to choose a name, profile picture, or accent color.
  • New subtitle "This password can't be recovered".
  • Removal of the checkbox "I understand my password can't be recovered"
  • The password should be limited to a maximum of 100 characters.
  • The code should pick a random accent color for the user.
  • The profile picture should be kept nil/unset.
  • The default name should be the compressed key, but without the prefix zQ3. For example shWiuC....rhf. Double-check with designers if this is in fact the correct expectation because Figma is outdated.

Resources

@Parveshdhull
Copy link
Member

should be implemented after #21571

@ulisesmac ulisesmac self-assigned this Nov 20, 2024
@ulisesmac
Copy link
Contributor

ulisesmac commented Nov 20, 2024

Starting with this to properly test #21571 later.

Update:
Figma for these is still in progress (🚧 icon). Waiting for it to be ready to start with both flows.

@ilmotta
Copy link
Contributor Author

ilmotta commented Nov 20, 2024

Figma for these is still in progress (🚧 icon). Waiting for it to be ready to start with both flows.

@ulisesmac My recommendation is talk directly with @xAlisher and start work on this as soon as possible because I thought we agreed on the flows. Maybe designers would like to adjust some details, but we don't have the luxury to wait much longer anymore if we want to include in 2.32 (which we do because in 2.33 we may not be able to prioritize this work).

@ulisesmac
Copy link
Contributor

@ilmotta OK! I'll align with @xAlisher to solve it 👍

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

Successfully merging a pull request may close this issue.

3 participants