Improve login/logout with Google experience.

[g-laures]

Is your feature request related to a problem? Please describe.

We are using Amplify web UI flow to login in our App with social provider, in our case Google.

Earlier this week we got a rejection from Apple app reviews saying that our login flow was not easy to use because it was not suggesting any Google account the user might be already using, which is normal since we set .preferPrivateSession().

So we tried without private session. The first issue we noticed is that now we have to open a page to logout. Also, if the user is trying to login again with Google, it auto logs him in unless he has more than one account.

Compared to native Google SDK, this is not a good user experience:

• Google SDK always asks you to confirm the account
• Google SDK never tries to open a page to logout, they simply wipe the keychain.

Describe the solution you'd like

What we would like is a similar experience as the Google SDK.

• Asking for the account could be a new parameter. Then when the Google login page is loaded it would add &prompt=consent to ask for confirmation.
• Do not open a web page when logging out. What we noticed is that you are inserting a "proxy Amazon page" before loading the Google login page and this page is then open again after successful login to store some values. Ideally this page would be removed and replaced by http calls on Amazon backend. This would probably require to import Google SDK which is fine.

Describe alternatives you've considered

At the moment we will be using non private session but we will have to cope with the cumbersome logout experience.

Is the feature request related to any of the existing Amplify categories?

Auth

Additional context

No response

[phantumcode]

@g-laures Thanks for submitting the feature request. We will investigate further and provide future updates here.

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[zhangshouyin]

@g-laures I have also encountered the same experience problem. Have you solved your problem? How to solve it?