-
Notifications
You must be signed in to change notification settings - Fork 739
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
Reduced onboarding steps #4590
Reduced onboarding steps #4590
Conversation
- may be temporary whilst evaluating login2
@@ -2509,6 +2509,7 @@ | |||
<string name="login_splash_text2">Keep conversations private with encryption</string> | |||
<string name="login_splash_text3">Extend & customise your experience</string> | |||
<string name="login_splash_submit">Get started</string> | |||
<string name="login_splash_already_have_account">I already have an account</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to complete our IRL discussion, https://github.com/vector-im/element-android/blob/main/vector/src/main/res/values/strings_login_v2.xml exists and so do https://github.com/vector-im/element-android/blob/main/vector/src/main/res/values/strings_login_v2.xml#L27. The resource from this file are not synced with Weblate, so feel free to do whatever you want with it, like removing strings for instance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closing for now, will reopen avoiding modifications to the base login flow |
Fixes #4382 Adding sign in to onboarding splash screen
Removes the Sign In/Sign Up step from the onboarding in favour of the
GET STARTED
andI ALREADY HAVE AN ACCOUNT
controlling the proceeding flowThis may be temporary, currently evaluating using
login2
insteadEDIT: chatted with @daniellekirkwood and @amshakal we'll go ahead with this small change as part of the main login flow with
the aim to have this change in users hands in the next release with the large remaining chunk of FTUE work taking place within
Login2