5 ms·
Why username / password? On mobile this is a dead approach. See https://docs.fabric.io/android/digits/digits.html https://docs.fabric.io/android/digits/digits.h
by harryf 11y ago
Why username / password? On mobile this is a dead approach. See https://docs.fabric.io/android/digits/digits.html https://docs.fabric.io/android/digits/digits.html
- tarr11 11y agoWhy is this better?
- harryf 11y agoUsers only need to remember their own phone number - you send a temporary activation code via SMS to register - as painless a signup as you can get Meanwhile it sets a higher bar than an email address for fakes signups; as a developer you have a higher degree of confidence that most of your signups correspond to a real person, which can help reduce abuse etc.
- spacehunt 11y ago"Invalid phone number". Nice try, but no.
- harryf 11y agoHuh? Digits (for example) supports over 200 countries - https://get.digits.com/international-growth https://get.digits.com/international-growth Twillio also enables this if you want to roll your own - https://www.twilio.com/blog/2015/01/mobile-passwordless-sms-authentication-part-1-building-the-api-with-laravel-and-twilio.html https://www.twilio.com/blog/2015/01/mobile-passwordless-sms-...
- spacehunt 11y agoYeah, it says it "supports" mine (Hong Kong) but whenever I type in my phone number that's what it says.
- ipapikas 11y agoWe have in mind that username can be a lot of things including email, a unique username or even a phone number. It depends on the approach but definitely under consideration in order to improve. Thanks!