@jbrooksuk@namzo it'll work internationally... some of our international friends here found a bug preventing the code from being sent to some countries. What's launching without the help of new friends to iron out some things, right? 😎 Try it again and you should be good to go.
This looks exciting to me. But I'm a bit naive as to the engineering realities. Hoping to see lots more comments here discussing use of this.
Report
@jimcanto There is more of an usability and trust issue here.
Implementing the mobile number as the prime authentification method is a huge emotional investment to ask from a prospecting user. This is not a commitment for 2-way authorization hence a second security layer that already ensured the user being involved and having a foot in the door in the users mentality. The mobile number has been shown to be a way more intrusive information to ask for then compared to an anonymous account and mail or oauth.
Report
@andmitsch Sounds like a good thing if one is interested in thwarting spam accounts within their app.
And, to your point; it would require the app be compelling enough to meet that trust threshold.
Interesting.
Report
@jimcanto@andmitsch I think I'd use it in my app (wip) if I make signup itself optional. Users can be onboarded without any signup and only asked to authenticate by phone number for a certain app feature when they clearly see value doing so. Not at the beginning of using a new app, I wouldn't give my phone number at first if I'm the user.
Report
@garyfung@andmitsch ...wouldn't give phone number? Even if you believed it would not be kept, used, or sold? Or would you simply not trust those promises at first?
Report
@jimcanto@andmitsch Wouldn't trust promises from a new app I don't know but just trying at first. And I'm speaking as putting myself in a normal user's shoes.
Laravel Artisan Cheatsheet
Copper
Copper
stoic.
Crypterval
Copper
Crypterval
Copper
Panda
ArtSquare
Sharechat
Mage
Sharechat