Skip to main content

General Features

This page talks about the standard features of both Vendor and Customer:

When the application is launched, Main Activity sends an intent to the Splash Activity, which displays the App Logo for 2000 milliseconds, from where the control comes back to the Main Activity. The app splash screen is the brief introductory screen that appears as the app loads after the user has just opened the app.






  1. Registration: 
    New users can register by entering their information. Their account gets created upon submitting the registration form. The new user fills out their e-mail ID, mobile number, and Password. They will select the type of user in a spinner. If the type of user is a vendor, they have to add a URL of the picture of their food outlet. Then on clicking register, a new account is created.




  2. Login:
    Users can log in using their Username. The user is directed to the Login Activity for authentication. The User first selects what type of user (i.e., Customer or Vendor) in the Spinner on the Login page. The Username for the customer would be their PhoneNumber, and for the Vendor, it would be their OutletName. Once the user clicks on the Login button, we verify if such an account with the given Username exists in the Database or not. If it doesn't exist, we display a Toast message saying, "No Account found". If the username is valid, then we verify the Password entered by the User by comparing it with the corresponding Password to the Username stored in the Database. If it is valid, then the User is redirected to their respective pages. 

  3. Login via OTP(Additional Feature): Users can also alternatively login via their Phone Number. We've used PhoneAuthProvider and PhoneAuthOptions for this purpose. They are classes defined by Firebase for the purpose of Phone Number verification.
    After the user enters their Phone Number, we verify if such a number exists in the Database or not. If the number exists, we send an OTP using the PhoneAuthOptions class. For the verification of the OTP, we use PhoneAuthProvider class to verify if the OTP entered by the user matches that of the one sent. On successful authentication, the user is redirected to the respective pages.



Comments

Post a Comment

Popular posts from this blog

App Architecture

App architecture is a consistent plan that needs to be made before the development process starts.  App architecture offers a road map for how the various application components must be set up and connected. It defines how the UI, database and background tasks interact to make the required job possible. We have used MVC(Model View Control) architecture to build our app.  MVC is known for handling multiple views and huge volumes of data effectively. There are three  components in MVC: Model : The model contains data about the application. All the information which must be stored or displayed and access specifications are mentioned here.  model.java serves as our model class. View : View forms the UI part of the app. Views displays model data to the users and allow them to modify the data. The Layouts form the view.  Controller : The controller handles user requests and controls user navigation within the app. It processes user input. The Activities and the Fragme...
Post a Comment
Read more

Database Design

Database designs provide the blueprints of how the data is going to be stored in a system.  Database design is a vital component of any app, and it determines what data to be stored and how the different data elements interact. A proper database affects the overall performance of an application. We're using a Firebase Database for our app. We prefer Firebase over SQLite since this is a multi-user app and FireBase is preferred over SQLite for Multi-User Apps.  Google Firebase is Google-backed application development software that allows developers to develop Android, IOS, and Web apps. It can be used for user authentication and to host a real-time database. The database design for our app is given below. The root node of our Database is Users, which branches into two children i.e. Customer and Vendor. We store all the information corresponding to the customer using the Customer's Mobile Number as the Key, and for vendor, we store all the information using the OutletName as the ...
Post a Comment
Read more

App Launch Screen

The app splash screen is the brief introductory screen that appears as the app loads after the user has just opened the app. When the application is launched, Main Activity sends an intent to the Splash Activity, which displays the App Logo for 2000 milliseconds, from where the control comes back to the Main Activity.   The MainActivity consists of three options: Login: Users can log in using their Username. The user is directed to the Login Activity for authentication. The User first selects what type of user (i.e., Customer or Vendor) in the Spinner on the Login page. The Username for the customer would be their PhoneNumber, and for the Vendor, it would be their OutletName. Once the user clicks on the Login button, we verify if such an account with the given Username exists in the Database or not. If it doesn't exist, we display a Toast message saying, "No Account found". If the username is valid, then we verify the Passwo...
Post a Comment
Read more