This topic is to discuss best practices for allowing users to "login" into the dapp or wallet
a patter that has not standardized solution yet
1- Alex Van de Sande - Universal Login Systems
@alexvandesande posted some thoughts on the Telegram about the "universal login system" which he talked about at the UX Unconference in Toronto
( please re-add here all your thougths and if you can also the questions Jonny and others had?! )
The basic version is:
- your wallet is a smart contract that you authorize from devices
- every device has it's unique private key (that you probably don't need to save?)
- from 1 device you progressively authorize many more
so the flow would be
- 1 - you create the wallet (and ID) on device 1
- 2 - you try to connect to it from device 2
- 3 - on device 1 you see that there is a request for authorization to the wallet and there, on device 1, you can authorize or deny it, you authorize it.
- now device 2 is recognized as being authorized
(probably in the local storage you have a key that is unique to that device)
- 4 - on device 3 you try to connect to the wallet
now you can have the same flow
and maybe set if you want to have multiple authorizations
- 4a - like authorize from device 1 AND device 2
- 4b - authorize from ANY other device
2 - Wallet Connect
@pedrouid and Richard Burton leads this initiative where as the user
* has a mobile wallet
* the dapp connects to the wallet through a QR that you have to read from your mobile phone
you can read more here: walletconnect.org,
join their forum here https://discuss.walletconnect.org/
or maybe @pedrouid you can give more info?!
3 - MetaMask
and a couple of Days ago Dan Finlay on Etherum Magicians
detailed a new login flow for situations in which Metamask does not inject the Web3 provider to avoid users be fingerprinted
There are a couple of UX opportunities in this system
read the whole post
4 - Login as education - The ENS case
at the Ethereum Name Service (ENS) we are creating a flow where the user does see a "LOGIN" button, but when they click it, a pop-up is shown to explain them that in the Web3 there isn't really the concept of a login and that you rather have to to "unlock your wallet"
and we offer, for now, the option to connect with Metamask, although other options will come.
The need for a "login" button came from the research phase: one of the most common questions user had was "where do I login?". So our approach is to give them a failsafe, a "login" button that will capture that mistake or behavior they are used to and educate them there about this different pattern of the Web3.
UI coming soon