3 ms·

It sucks. Another horrible pattern is that enter email, hit enter THEN we'll show you the password field. What kind of puddinghead cooked that up I wonder.

runjake 3y ago
Here's what Google said when they implemented it: "Today, you sign in to Google on a page that includes both the ‘email’ and ‘password’ fields on the same page. We’ll be gradually splitting those two fields into separate pages in the coming days; the sign-in process won’t change otherwise. As we’ve said many times, we're working towards introducing new authentication solutions that complement traditional passwords. We’ve already separated the ‘username’ and ‘password’ fields onto separate pages on a successful launch in Android last year. This change to our web sign-in page is another step in that direction. To help make sign-in easier and more personal, you may see a screen with your profile picture and full name when signing in to Google. We’ll only show this information if you are signing in from a location or device you’ve signed in from before, like your home computer." I have no opinions on it. At least, no positive opinions.
- sergiotapia 3y ago
  Crazy they just skip past the why. Why split it in the first place lol
  - runjake 3y ago
    They state why, albeit poorly worded and justified: > we're working towards introducing new authentication solutions that complement traditional passwords Anyway, terrible explanation on Google's part, IMHO.
  - Moomoomoo309 3y ago
    My college uses this. It redirects to their login system when you put your school email in on gmail.
codingdave 3y ago
I've done this. It really isn't to make life difficult, it is because we need to know who you are before we know whether you even need a password screen. Maybe your domain means you are part of an org has an SSO connection configured. Maybe you are not yet a user and need an onboarding workflow, etc. Could that be done on a single page instead of a new page? Probably, but does turning the login into an SPA really reduce friction enough to make it worth that complexity? In any case, some systems have a reason. But you are correct that doing such a thing without a good reason is not a wise move. And outside of B2B apps... I don't see it being a common thing.
codegeek 3y ago
Sometimes that is needed if you offer native login and SSO to login. Once a user enters the email, the system then checks if they should go to the SSO flow or normal password flow.

runjake 3y ago

Here's what Google said when they implemented it: "Today, you sign in to Google on a page that includes both the ‘email’ and ‘password’ fields on the same page. We’ll be gradually splitting those two fields into separate pages in the coming days; the sign-in process won’t change otherwise. As we’ve said many times, we're working towards introducing new authentication solutions that complement traditional passwords. We’ve already separated the ‘username’ and ‘password’ fields onto separate pages on a successful launch in Android last year. This change to our web sign-in page is another step in that direction. To help make sign-in easier and more personal, you may see a screen with your profile picture and full name when signing in to Google. We’ll only show this information if you are signing in from a location or device you’ve signed in from before, like your home computer." I have no opinions on it. At least, no positive opinions.

sergiotapia 3y ago
Crazy they just skip past the why. Why split it in the first place lol
- runjake 3y ago
  They state why, albeit poorly worded and justified: > we're working towards introducing new authentication solutions that complement traditional passwords Anyway, terrible explanation on Google's part, IMHO.
- Moomoomoo309 3y ago
  My college uses this. It redirects to their login system when you put your school email in on gmail.

codingdave 3y ago

I've done this. It really isn't to make life difficult, it is because we need to know who you are before we know whether you even need a password screen. Maybe your domain means you are part of an org has an SSO connection configured. Maybe you are not yet a user and need an onboarding workflow, etc. Could that be done on a single page instead of a new page? Probably, but does turning the login into an SPA really reduce friction enough to make it worth that complexity? In any case, some systems have a reason. But you are correct that doing such a thing without a good reason is not a wise move. And outside of B2B apps... I don't see it being a common thing.

codegeek 3y ago

Sometimes that is needed if you offer native login and SSO to login. Once a user enters the email, the system then checks if they should go to the SSO flow or normal password flow.