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

What is Diner2Door?

There are a good number of food outlets in BITS Pilani Hyderabad Campus and they are very popular among students. This in turn results in high waiting time for customers. Also, this leads to decreased revenue for outlets since people choose not to utilize the outlets due to the long waiting time. Our Solution? Diner2Door is an app created to solve this problem. The users can order from their favorite outlets using our app from the convenience of their own rooms. We made two separate pages for both the vendor and the customer where the vendor can change the menu based on availability and the customer can choose their favorite outlet and order food from their rooms.

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

App Features(Customer)

Here, we talk about the Customer's side of the app: The customer Homepage contains a fragment that displays the corresponding layout of the item clicked in the sidebar. As soon as the customer is logged in OutletList Fragment is called which displays the list of outlets present, where clicking on a particular outlet, will take them to the particular menu of the outlet. We've used Firebase UI in all fragments. Firebase UI is a class provided by Firebase SDK to make a query in the database to fetch appropriate data. Based on the customer's requirements and usability, we have developed an exclusive set of fragments. OutletList: This fragment will be called after the user is logged in. It will consist of a list of eateries that are open at any given time. It contains a recycler view, which populates itself using outletList_adapter by querying the List of Vendors in the Database using Firebase UI.  OutletMenu: On selecting one of the outlets, this fragment is called which di