Open landsman opened 2 years ago
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Reading: https://tech.oyorooms.com/implementing-automatic-sms-verification-for-websites-oyo-9375feba0749.
This is current problem of sms templates: A special format of message is required to use Web OTP API.
Interesting part about performance:
Lets talk about numbers
Post implementation, following are the two major data points which we are able to observe:
1. Login funnel has improved by 6.09% which is basically from the time user lands on login page to the login success page.
2. Login time is reduced by 37%.
Thanks for this issue, this is a feature request that we're already tracking on our roadmap but I can't give any estimation of timeline. For Google folks: b/156500337 is tracking.
Can we somehow help you with that? I am missing basically just specification what have to be done on where.
Can we somehow help you with that? I am missing basically just specification what have to be done on where.
Thanks Michal! We currently need to get the public API changes approved. Once that is done, we can circle back with more details on the changes to be made. Any PRs will be welcome at that point. Thanks for your patience on this.
Describe my environment
Android 9
Chrome 103.0.5060.129
9.9.0
auth
There is no possibility to use SMS OTP "autofill" on Android. It's working on iOS because they have native support for reading SMS with text: "code: xxx" but on Android you have do the trick to make it work.
I am in shock that Firebase, company of Google, founder of Android do not have this automatically. For me, and I know that I am not alone, it's a big UX blocker for our users.
I would love to see this kind of bug (not a feature request) somewhere publicly. So GitHub is the great place I think.