[ad_1]
To get this product on 50 p.c low cost contact me on this link
Features
-
Authentication by Phone Number
- Users can Sign-In into your software utilizing their Phone Number.
- It will inquire of for the User’s present location. After permitting that person’s nation code and the extension shall be proven.
- User can decide any nation from a Country Picker and Sign In.
- reCAPTCHA will seem mechanically if the person tries to make a number of requests concurrently.
- A verification code shall be despatched to the Phone Number.
- A timer consisting of 60 seconds shall be began. Users must enter the code inside that point span.
- After 60 seconds a “Resend Code” button will seem and the person can resend the verification once more.
- After profitable entry, it should create a brand new person if the Phone quantity hasn’t used but.
- If the Phone Number already used then it should fetch person particulars from database.
- Now it should convey customers inside your software.
-
Authentication by Email Address
- Users can Sign Up or Sign-In into your software utilizing their Email Address.
- The e-mail tackle checker will examine for a sound e-mail tackle and knowledgeable customers for correction accordingly.
- The password energy checker will examine for a robust password and knowledgeable customers if the password is weak or intermediate.
- “Forgot password” will ship a hyperlink to the person’s emails for getting a brand new password.
- In the Sign Up course of, all essential checks are there like, e-mail validation, matching password, password energy checker, and knowledgeable customers for correction accordingly.
- If the e-mail is already in use, then it should present the platform (Email/Google/Twitter) by which the e-mail tackle was used earlier than for authentication.
- After profitable entry, it should create a brand new person for Sign Up and ship a hyperlink to e-mail for e-mail verification or Fetch person particulars from the database for the present e-mail tackle.
- Now it should convey customers inside your software.
-
Authentication with Google
- Users can Sign-In into your software utilizing their Google account.
- After profitable entry, it should create a brand new person if the Email Address hasn’t used but.
- If the Email Address already used and the earlier auth sort is Google, then it should fetch person particulars from the database.
- If the Email Address already used and the earlier auth sort will not be Google, then it should present an alert the place it should say “There is an account in our database with this email address and that information will be replaced with your current Google Account’s information.”
- After profitable entry, it should convey customers inside your software.
-
Authentication with Facebook
- Users can Sign-In into your software utilizing their Facebook account.
- If Facebook App is put in within the machine then it should open it and redirect the person there in any other case it should open in Web.
- If the e-mail is already in use, then it should present the platform (Email/Google/Twitter) by which the e-mail tackle was used earlier than for authentication.
- After profitable entry, it should create a brand new person if the Email Address hasn’t used but.
- If the Email Address already used then it should fetch person particulars from database.
- Now it should convey customers inside your software.
-
Authentication with Twitter
- Users can Sign-In into your software utilizing their Twitter account.
- If Twitter App is put in within the machine then it should open it and redirect the person there in any other case it should open in Web.
- If the e-mail is already in use, then it should present the platform (Email/Google/Facebook) by which the e-mail tackle was used earlier than for authentication.
- After profitable entry, it should create a brand new person if the Email Address hasn’t used but.
- If the Email Address already used then it should fetch person particulars from database.
- Now it should convey customers inside your software.
-
User Profile
- Auth Credentials: Email Address or Phone Number.
- Joining Date: Profile Creation time & date.
- User Name: It will fetch User title for Google, Facebook & Twitter Authentication. For telephone and e-mail initially, it will likely be clean.
- User Profile Image: It will fetch User Profile Image for Google, Facebook & Twitter Authentication. For telephone and e-mail initially there shall be no profile image. User can set new profile image and delete it as effectively.
- Password: Only seem for Email Authentication.
- Auth Type: Logo.
- Address: Initially clean.
- isEmailVerified: Only seem for Email Authentication. If the person verifies it from his/her e-mail then it will likely be inexperienced and say verified in any other case you’ll be able to ship a brand new verification e-mail from there as effectively.
- Update Profile
-
Update Auth Credentials: Users can replace Email Address or Phone Number.
- Email replace: To change Email tackle customers will need to have to confirm the present Email first. Then they will set new Email tackle by offering info on “Password”, “New Email Address” & “Confirm New Email Address” textual content discipline. Then a verification e-mail shall be despatched to the New Email tackle to confirm.
- Phone Number replace: To change Phone Number customers will need to have to confirm the present Phone Number first by offering PIN code. Then customers can set new Phone Numbers and to efficiently change it customers have to supply PIN code which shall be despatched to the brand new Phone Number.
- User Name: User can set or edit it.
- User Profile Image: Users can set new profile image and delete it as effectively.
- Password: First have to offer outdated password for verification. Then customers can set new password by offering info on “Password” & “Confirm Password” textual content discipline.
- Address: User can set or edit it.
-
Update Auth Credentials: Users can replace Email Address or Phone Number.
-
Tab Bar
- Home View Controller with a tabbar controller the place three different tabs exists.
-
Others
- Scalable for all iOS units
- Clean UI/UX
- 100% bug & error-free
- In particulars step-by-step youtube video Tutorial (Documentation)
- From scratch to combine it into your personal challenge
- 24/7 obtainable assist
Documentation
-
Download these two recordsdata
Firebase Cloud DataBase Permissions
&
Firebase Storage Permissions - Then comply with the directions steps by step from this Tutorial (Documentation)
Required Skills
- Swift
- Xcode
- Pod
- Firebase
- Firebase Authentication
- Firebase Database (Cloud Firestore)
- Firebase Storage
- Firebase Rules & Permissions
- Apple Certificate (Message push notification for Phone quantity)
- Facebook SDK
- Twitter SDK
Others
- Swift 5
- Deployment Target 11.0
- Paid Apple developer account
Support
- Tutorial (Documentation)
- For Support: [email protected]
Project Updates
-
Version 1.0.0 – Released on 1 June 2020
1. - Initial Release
[ad_2]
To get this product on 50 p.c low cost contact me on this link