You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current user experience is not great. We should let somebody with some experience designing UX look through the user flow and UI and come with improvement suggestions.
Other bankid login solutions often give a set of options allowing the users to select how they want to login. This normaly includes one or more of the following options.
BankId on this device
BankId on another device
Mobile BankId on this device
Mobile BankId on another device
Option 1 and 3 is technically the same from the point of view of the BankId Keycloak provider. However perhaps there is a UX purpose to give the user both options since BankId (on a Windows desktop or laptop) and Mobile BankId is marketed as different things to the end users.
Option 2 would require the use of the use case that starts with the end user entering their "personal identity number". Since this is already discouraged and will no longer be supported in the RP v6 API perhaps we should skip this option.
For more information on the UX guidelines from BankId see technical integration guides which includes suggestions, perhaps even requirements, about the UX in the several of the chapters. Especially interesting for the UX is the chapters "Use Cases", "Launching", "User Messages", "Support" and "Terminology".
The text was updated successfully, but these errors were encountered:
The current user experience is not great. We should let somebody with some experience designing UX look through the user flow and UI and come with improvement suggestions.
Other bankid login solutions often give a set of options allowing the users to select how they want to login. This normaly includes one or more of the following options.
Option 1 and 3 is technically the same from the point of view of the BankId Keycloak provider. However perhaps there is a UX purpose to give the user both options since BankId (on a Windows desktop or laptop) and Mobile BankId is marketed as different things to the end users.
Option 2 would require the use of the use case that starts with the end user entering their "personal identity number". Since this is already discouraged and will no longer be supported in the RP v6 API perhaps we should skip this option.
For more information on the UX guidelines from BankId see technical integration guides which includes suggestions, perhaps even requirements, about the UX in the several of the chapters. Especially interesting for the UX is the chapters "Use Cases", "Launching", "User Messages", "Support" and "Terminology".
The text was updated successfully, but these errors were encountered: