Is there a solution cheaper than using firebase phone number verification.
SMS pricing is high after free plan.
Then I found TextNow but its not working in India.
How other applications verifiy phone number at cheaper costs mostly the OTP comes from virtual phone numbers.
Is there a way I can verify phone number other than otp or any cheaper api ?
Related
I applied user authentication with phone number in my flutter app using firebase, but the SMS with the one time password service is limited to 50 SMS/day, so I wanted to find a way to authenticate by phone number without firebase. its possible
I tried searching for ways to authenticate with phone number but all the results I found were using firebase
I works for a bank that is considering using an instant app (and AppClip on iOS) to provision a newly approved credit card with both our card App and Google Pay. I know you cannot take payments, but does that mean you are locked out of TapAndPay completely? Would you be able to provision a card in Google Pay from an Instant App?
So after communication with Google Tap and Pay support, and trial and error -- the answer is yes. You can access TapAndPay; however, you can not recieve or make payments from an instant App.
Hi im working on a phone number based android app,
Im currently using google firebase.
Google firebase is pretty expensive when it comes to phone authentication,
I was thinking if there are any other ways to authenticate a phone number.
Programmable sms like twilio is fairly cheaper but still pretty expensive for my budget.
Is it possible to use voip to auth a phone number?
Are there any other alternatives?
Using twilio is right option for limited number of sms for your purpose, as for voip they all depend on SMS gateways, and to have gateway which may be cheaper but require massive sms, as they are more expensive.
I'm using twitter developer API for my project. I have created an account with my phone number and email address. As you know there are some rate limits in twitter API!
For using API I should create app and user tokens of that app.
My question is that if I create multiple apps for that single account and use them in my project, my rate limit is multiplied by number of apps or requests are aggregated so my rate limit doesn't change?
Yes. It is limited by account.
Rate limiting of the standard API is primarily on a per-user basis —
or more accurately described, per user access token. If a method
allows for 15 requests per rate limit window, then it allows 15
requests per window per access token.
See: https://developer.twitter.com/en/docs/basics/rate-limiting.html
Does Google's SMS Retriever API get the list of phone numbers from the SIM lines on the user's device (which means that it's similar to TelephonyManager), or from the user's Google Play account?
I'm the product manager at Google for this API. Yes, as of the latest version of Play Services, the Phone Selector shows both the phone number for the device from the TelephonyManager (if it can be parsed as as a valid phone number) as well as recent phone numbers for the active Google Accounts on the device.
This is not directly addressed from the docs but if we infer from this statement in the Obtain the user's phone number:
Often, it is the best user experience to use the hint picker to prompt
the user to choose from the phone numbers stored on the device and
thereby avoid having to manually type a phone number
we can deduce that SMS Retriever API gets the contacts from your device.
Update
Please look at #Steven Soneff's answer
The numbers are retrieved from Smart Lock for Passwords on Android. They are retrieved if the user already stored it using Smart Lock else they will be empty. You may also ask the user to store the number for future use-cases using Smart Lock for Passwords.