In India at least, people rarely change their number. They change their handsets/devices, their operators, but not their numbers. (Number Portability is allowed in India and many other countries).
And in rare cases, when a user does happen to change his number, and opens any app which was attached with his old number, he is given OTP option (in which his old number will receive an OTP one last time); or security questions (in which he’ll be asked a few security questions). And this way he can effect the number change.
As part of the broad PWA Spec, browsers will be able to read one-time passwords from SMS using a new web API. This is coming this year to Chrome on Android, and was created to deal with cases like this.
As we experience first hand in India in an average district, majority of these new users have to get someone to create an account on Gmail, just because they want to use WhatsApp and WhatsApp cannot be downloaded unless you’ve a playstore login ID (that’s =Google id).
And thereafter they never sign in to their Gmail. Not even once. For all purposes, they never know what’s their id is (far is password).
And sometime, for whatever reason, they happen to logout of their account on android, and they need to login once again in their Gmail account, they keep carrying their Mobiles to different known persons, requesting them to help start their mobile again. (they consider their mobile to be not usable if either WhatsApp stops, or calling stops)
We would be extremely happy to take place in any plugin experiment. How would we proceed to find someone to author it? Do we need to fund the SMS gateway for phone validation?
Please advise. I think it’s worthwhile testing it and see the uplift in registrations, as opposed to continue the debate. There’s a reason why Fcaebook / whatsapp offer it.
As far as notifications go, considering now that we have browser based notifications, at least there’s an alternative. Looking into occasional SMS notifications is not a bad idea, though I don’t think it’s the priority right now. I would expect it could start with a weekly or monthly reminder that there are new updates (if user hasn’t visited the community) and take users to their notifications page. Easy optout would be needed. Again, I wouldn’t include this in the plugin mvp.
Sorry, I should have clarified above - those figures aren’t ‘email accounts created in India’, that’s the number of unique mobile device users actively connecting to email devices every month.
Those figures are also against the total Indian population for 2018 of 1.344 billion. Measured against the 566 million internet users in that same period, the number of active email users is just over 35%.
The idea is not to use SMS as a password, but to simply replace the sending of emails with sending SMS through Twilio, Africa’s Talking, and Braze campaigns. The first two are currently implemented and seem to be working well. The last is currently in development.
The concept is to hide the email address on sign-up and fill it in behind the scenes with addresses that mimic the phone number: email@example.com. That way Discourse still works with emails if it needs.
But then we tie into specific events (user creation, password update, PM sent, mentions, etc…) and send SMS notifications on top of the email. But since the email is going to the aliased email, the user never has to deal with it.