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

Change logo to WordPress.com when logging in to WordPress.com #4742

Closed
kwonye opened this issue Nov 2, 2016 · 3 comments · Fixed by #4851
Closed

Change logo to WordPress.com when logging in to WordPress.com #4742

kwonye opened this issue Nov 2, 2016 · 3 comments · Fixed by #4851

Comments

@kwonye
Copy link
Contributor

kwonye commented Nov 2, 2016

To match wordpress-mobile/WordPress-iOS#6142

We'll switch the logo based on what log in screen the user is currently in

@hypest
Copy link
Contributor

hypest commented Jan 10, 2017

Reopening this as currently, the app does show the logotype, but shouldn't do it on the initial login screen. The .com logotype should appear only after the app has detected that this is indeed a .com login.

@mattmiklic , can you share more info on the desired flow? Thanks!

@hypest hypest reopened this Jan 10, 2017
@mattmiklic
Copy link
Member

mattmiklic commented Jan 10, 2017

In short: the first screen of the app can accept logins for any kind of WordPress blog; self-hosted or WordPress.com. We don't want to give a mistaken impression as to what kinds of accounts are supported. So the first screen should include the (W) mark alone. After entering a WordPress.com username or email address, the next screen should show the WordPress.com logotype. After entering a username or email address not associated with a WordPress.com account, we should show the existing self-hosted login screen. A visual representation of the flow is below.

flow

Let me know if you have any other questions, happy to clarify!

nbradbury added a commit that referenced this issue Mar 9, 2017
Login: Show logotype only when showing wpcom password form.
@hypest
Copy link
Contributor

hypest commented Apr 21, 2017

Fixed with #5353

@hypest hypest closed this as completed Apr 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants