Carlos Macêdo
I want you to always enter the phone number when you log in. Well, in your apk, once I logged in with the phone x. will always log in with the same number. Is this behavior inert to its implementation or will it always occur like this?
ionFirebaseAccountKitPhoneAuth
Ionic3 Firebase Phone Authentification
$15.00
Not yet rated
radiarama
Member since 2017
Details
Awesome starter that allows you to provide phone authentication without captcha in your ionic mobile app Firebase by using Facebook AccountKit.
Firebase Plan However, this starter won’t work with Spark plan as external network is not accessible on free plan. We need to validate Account Kit's token. So you have to switch your Firebase project to Blaze plan (pay as your go) as it has some free tier with Cloud Functions, so that you should not be billed.See here : https://firebase.google.com/pricing
Please see the README file in the main download file to get it works.
Test before you buy
: https://drive.google.com/file/d/0BwqiYMfGZgEhb2lucExoMW5NcnM/view?usp=sharingSupport If you need technical support or have any questions, please send us a message via: radiarama2017@gmail.com
Hey there! You'll need to log in before you can leave a comment here.
Carlos Macêdo
I want you to always enter the phone number when you log in. Well, in your apk, once I logged in with the phone x. will always log in with the same number. Is this behavior inert to its implementation or will it always occur like this?
Carlos Macêdo
Firebase charges for more than 10mil log-in /month. You use Facebook AccountKit. Will facebook charge something too? or the login cost remains the same, ie just the firebase.
Papa Cheikh Cisse
No for this starter, firebase won't charge anything else than the cloud functions pricing. For the phone authentication, we use facebook accountkit which remains free until August 2018 according to facebook. Past this date, standard SMS charges will apply for apps exceeding 100,000 confirmation messages. See this article in The next web: https://thenextweb.com/dd/2016/08/16/facebook-account-kit-pricing-2018
radiarama
Hi carlos, However, this starter won’t work with Spark plan as external network is not accessible on free plan. We need to validate Account Kit's token. So you have to switch your Firebase project to Blaze plan (pay as your go) as it has some free tier with Cloud Functions, so that you should not be billed. See here : https://firebase.google.com/pricing
Sistemas Radecom
I am interested in buying it for the current version of Ionic 5. Will you have it for Ionic 5?
Sistemas Radecom
I am interested in buying it for the current version of Ionic 5. Will you have it for Ionic 5?
Carlos Macêdo
I want you to always enter the phone number when you log in. Well, in your apk, once I logged in with the phone x. will always log in with the same number. Is this behavior inert to its implementation or will it always occur like this?
Carlos Macêdo
Firebase charges for more than 10mil log-in /month. You use Facebook AccountKit. Will facebook charge something too? or the login cost remains the same, ie just the firebase.
Papa Cheikh Cisse
No for this starter, firebase won't charge anything else than the cloud functions pricing. For the phone authentication, we use facebook accountkit which remains free until August 2018 according to facebook. Past this date, standard SMS charges will apply for apps exceeding 100,000 confirmation messages. See this article in The next web: https://thenextweb.com/dd/2016/08/16/facebook-account-kit-pricing-2018
radiarama
Hi carlos, However, this starter won’t work with Spark plan as external network is not accessible on free plan. We need to validate Account Kit's token. So you have to switch your Firebase project to Blaze plan (pay as your go) as it has some free tier with Cloud Functions, so that you should not be billed. See here : https://firebase.google.com/pricing
Carlos Macêdo
I want you to always enter the phone number when you log in. Well, in your apk, once I logged in with the phone x. will always log in with the same number. Is this behavior inert to its implementation or will it always occur like this?