3 ms·
This is a worthy goal as I'm sold on passwordless mechanisms too. Not a telecom provider leaking your SMS codes, not email provider resetting your pass
by sriku 9y ago
This is a worthy goal as I'm sold on passwordless mechanisms too.
Not a telecom provider leaking your SMS codes,
not email provider resetting your passwords, not
Facebook Connect/Google OAuth issuing your access_token
to someone else.
We also need to consider someone who just has access to your phone unlocked .. even if it be your "harmless" kid :) It looks like in the current design, there is no additional safeguard for this - like using a device's finger print scanner.
- homakov 9y agoYou're right, there's no custom passcode on purpose (short post why not https://medium.com/@homakov/against-passcodes-in-apps-a76b9a00b242 https://medium.com/@homakov/against-passcodes-in-apps-a76b9a...) If more people need it it will be added.
- sriku 9y agoThat's an interesting recommendation that sounds valid. I'm unsure of the user experience - in particular whether a user is likely to be confused by being thrown back to the system unlock. Any notes on non-techies dealing with this in your experience?
- __m__ 9y agoYou are right, but this is easy to solve. The less nice solution is to show a little explanation before locking the device, the better one depends on OSes. They should simply provide a way for devs to trigger the lock screen for this specific purpouse and let devs specify a message, color scheme, theme, logo, whatever that needs to feel the lock mechanism more integrated in the app.