id - basic condition (if id boughts - not access) - it's possible to create new account
ip address (if ip address bought - not access) - it's possible to change ip/have a changing network
VISA - (if VISA boughts - not access) - it's possible to create new card
Telephone Number (Pin system(?))
If you connect those 3 conditions -...
I see no reason to deal with passwords if you have OAuth / magic link, you simply dont need password (and therefore dont need your user to pick password after OAuth login for sure)
Generate and send password is also not convinient: try open your inbox and find StackExchange registration email.
Every time you send magic link, it has to contain new access ...
Hi Michael Joseph Aubry,
When evaluating approaches like this, it's best to blur the lines between usability and security.
Is the magic link and passwordless a good UX? Yes it is. The best way to create a secure UX is to make it seamless. Fingerprint, magic link e.t.c are both relatively secure and usable, they lift the cognitive burden from the user of ...
Best option: Keep both handy
You can decide to show Login/Registration either based on data (first time use vs login token)
Or based on whether the app has a higher traffic web platform
Or based on expectation of the user via a bit of user research
BUT always keep the alternate option handy. Either with a tab-like switcher or a simple link.
Notice how ...