You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we are simplifying the onboarding journey, the user will have a default display name based on their compressed key, as well as a default random accent color (see issue #21567).
Before the user sends a contact request or send a message to somebody, we should ask the user if they want to update their profile.
Acceptance criteria
We ask only once if the user wants to update their profile. Use async storage because this choice doesn't need to be persisted in status-go.
Once the user finishes editing their profile, they should be automatically redirected to their original intent (either send contact request or open bottom sheet to add contact/new chat)
Confirmed with Volo that this issue 21571 is not a requirement for 2.32 because users will still be able to edit all their profile data after onboarding. On the other hand, issue #21567 is a must have for 2.32.
Given this plan @ulisesmac, the best is to completely ignore this issue (21571) and focus on #21567. Only once #21567 is merged we should come back to #21571.
Feature
Description
Now that we are simplifying the onboarding journey, the user will have a default display name based on their compressed key, as well as a default random accent color (see issue #21567).
Before the user sends a contact request or send a message to somebody, we should ask the user if they want to update their profile.
Acceptance criteria
Resources
The text was updated successfully, but these errors were encountered: