SOLIDUI: Optimise the design of Solid login page

[tonypioneer]

Description

We can refer to the user interaction designs of many websites and app login pages to optimise the design of the Solid login page.

1. They request the user to actively "Stayed signed in (not recommended for shared devices)", if the user wants to.
2. They request the user to "Try another account" to sign in using a different ID:

A couple of observations:

• As mentioned in our meeting, the "Continue" button is useful for the apps' features that do not require interaction with a POD.
• Either issuing a new login or logging in with a cached, authenticated ID, the user must always know the flow and what action the app will perform (the UI should be simple and intuitive).

Originally posted by @srodriguez142857 in #217

[tonypioneer]

Perhaps the workflow should be

• If I click “Login” and there is cached login information for the specified server, the app will use that cached information and proceed. If I checked “Stay signed in” before logging in, the login information will remain in the cache; if I unchecked “Stay signed in” before logging in, the cached login information will be removed and I will need to log in again next time.

• If I click “Login” and there is cached login information for a different server, a new login will be initiated via the browser.

• If I click “Try another account”, the cached login information will be cleared, and I will be redirected via the browser to the username and password input page to log in with a new account.

• If I click “Login” and there is no cached server information, the login process will be initiated via the browser. If I checked “Stay signed in” before logging in, the login information will be saved in the cache; if I did not check “Stay signed in”, the login information will not be stored and I will need to log in again next time.

• If I click “Continue” and cached login information exists, the app will use that cached information.

• If I click “Continue” and no cached login information exists, I will continue using the app until a login is required, at which point I will be prompted to log in.

[srodriguez142857]

Thanks, Tony. This looks good and, I think, covers most common authentication use cases.

[tonypioneer]

When the user clicks "try another account", he/she can only be navigated to the page on the server as below.

The user can select another WebID under his/her account, or click on the "Other WebID" button to log into another account.

So I think the text "try another account" can be changed to "try another WebID".