abdulhannanali / authyfire-passwordless Goto Github PK

Add a README.md file which explains about the project and the source code in it. This README file can be a starting point for our application and how we deal with different components represented within the README file.

Front end for this application is just to demonstrate the proper working of the application. The more important part in this application is about Firebase Functions so more importance should be paid to explain the working of functions within our application.

Some of the todos that can make the README.md file comprehensive

• Basic information about the project
• Different components of the Project
• Explaination about the functions and how they are managed
• Keep it to single page (This is the first version so keep it simple)

There are a bunch of Authy related errors, we should consider and provide appropriate validation for each of the errors, that might be important for the user, so they can stop trying.

Right now, if the user is banned for any reason known by Authy the error displayed will be in the lines of 503 Server Error but this is clearly not a server error, but a legitimate ban by the Authy. This should be displayed accordingly as it'll improve the user experience in many ways.

When the page loads, we should make test calls to the functions, and check if they exist. This way the user can be notified if the application is usable or not, by displaying appropriate information to the user.

The inputs right now, aren't validated before entering some value into them. This leads to some very unnecessary input requests which are totally useless. Having pre request validation can lead to avoidance of many extra requests to validate stuff.

Implementing this application with a blog post in mind, so it's important to keep things simple always in this application.

The ProfileView currently only supports a display of a few of the fields that are there. This ProfileView component which is used in user dashboard can be made much more interactive for us to use.
This component can additionally support modification of fields such as Name, email etc. for the user.

List of the tasks we can do to make this more interactive

• Replace the Text elements with Form elements
• Add the interactive state fields within the application

When the account is first created we use a placeholder email to identify the user, but whenever the user adds their own legitimate email. We should add this email to the user's given Authy ID, in order to keep the representation consistent and let Authy know of the different behaviors being performed.

A high priority feature I plan to work on, in order to update the data for a phone number any time an authentication is performed for a given client.

Why is this data important?
This data will allow us to make better decisions regarding the authentications, such as when the user is excessively attempting for a token, we can ban the user, even before Authy doing this for us, or this data can be helpful for the messages, as well as analytics too. Lots of usage.

Sometimes the SMS isn't received by the user, we want to make sure, they get and make proper use of the SMS for their purpose.

More data in authyRef token, will allow us to better manage our login session and show more helpful messages to the user. Something we will do after the first iteration of this is done.

I am going for React in the UI.

Why React is a good choice?

• It keeps things declarative
• Declarative syntax makes it easier for people to understand the code
• Provides something from state management
• Isn't a complete framework
• I know it already.

Although, I think I should do it in DOM. It's a damn hard and time consuming approach for me. So React is the option.

Here are a few tasks I have to complete for this checklist.

• Implement the request module for sending the requests in the application
• Determine how the UI looks like Mocks and Stuff
• Determine the Components going to be used within the Application
• Determine the State that's going to be included within the Application
• Code the Components and Integrate them

Additional features

• Implement the additional reenter and resent features for VerifyControl component

Force SMS functionality is important once in case the user is not currently on it's smartphone, we need a way to reach the user somehow.