Skip to main content

App Features(Vendor)

Here we talk about the Vendor's side of the app: 

The Vendor Homepage contains a fragment that displays the corresponding layout of the item clicked in the sidebar. As soon as the vendor is logged in OutletMenu Fragment is called which displays the menu of the vendor's outlet, where the vendor and add, update and delete items from his menu.





Based on the customer's requirements and usability, we have developed an exclusive set of fragments and an activity.

    1. OutletMenu: This fragment will be called default after the vendor is logged in. It displays the menu of the vendor's outlet. It contains a recycler view, which populates itself using outletMenu_adapter by querying the Menu corresponding to the vendor's outlet in the Database using Firebase UI. The vendor also has the option to edit and delete items from the existing menu. When the vendor clicks on the edit option, a Dialog using DialogPlus class is built and the current values are retrieved from the databases and set to the EditText. Upon performing the necessary changes, we call the updateChildren function to update the menu to the new values. When the vendor clicks on the delete option, a dialog pops us using the AlertDialog, to confirm the deletion of an item from the menu.

    2. AddItem: When the vendor wants to add a new item to the menu, he clicks on the FloatingAction Button on the bottom right, whereupon an intent is sent to open the AddItem activity. This takes in the input of the Name, Price and URL of the picture of the new item to be added. On Clicking Add button, it gets stored in the Database.

    3. TransactionHistory_Vendor: This fragment displays information regarding the previous orders received by the vendor. It displays the Phone Number of the Customer, Total Amount and the Transaction ID of the order.  This fragment contains a recycler view, which populates itself using TransactionHistory_Vendor_Adapter by querying the Transaction History details of the particular outlet using Firebase UI. 


Comments

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...

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 ...

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...